When the keystone server was configured to use the LDAP assignment
backend and a role was modified with the same name as the role the
operation would fail. This is because the server would check that a
role with the same name existed already and it would of course find
the entry that is currently being modified.
The server is changed to check if the entry currently being modified
is the one with the same name and the operation is allowed if this is
the case.
(cherry picked from commit b6f7cad8ba432e6d3e33812238620e768c529996)
Reviewed: https:/ /review. openstack. org/142556 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=44c1bd0c8d0 29f8fb420f78948 403eb3d86f84fd
Committed: https:/
Submitter: Jenkins
Branch: stable/juno
commit 44c1bd0c8d029f8 fb420f78948403e b3d86f84fd
Author: Brant Knudson <email address hidden>
Date: Thu Dec 11 19:18:45 2014 -0600
Fix modifying a role with same name using LDAP
When the keystone server was configured to use the LDAP assignment
backend and a role was modified with the same name as the role the
operation would fail. This is because the server would check that a
role with the same name existed already and it would of course find
the entry that is currently being modified.
The server is changed to check if the entry currently being modified
is the one with the same name and the operation is allowed if this is
the case.
(cherry picked from commit b6f7cad8ba432e6 d3e33812238620e 768c529996)
Change-Id: Ia86ef9fabfd438 367a7ed09efb557 11860e47d8b
Closes-Bug: #1401721