Identity LDAP does not support AD nested groups
Bug #1638603 reported by
Adam Young
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Adam Young | ||
Newton |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Active Directory has a very specific mechanism to
handle nested groups. LDAP queries need to look like this:
"(&(objectClass
If a deployment is using nested groups, three queries need to be modified to support it:
list users in a group
list groups for a user
check if a user is in a group
Since all three are necessary, a single configuration value ensures
that the change is synchronized across all three calls.
Changed in keystone: | |
milestone: | none → ocata-1 |
importance: | Undecided → Medium |
assignee: | nobody → Adam Young (ayoung) |
status: | New → In Progress |
Changed in keystone: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
To test the calls on a live server:
curl -H "X-Auth-Token: $AUTH_TOKEN" $OS_AUTH_ URL/users/ $USERID/ groups
and
openstack user list --group