Filter LDAP attribute queries in existing LDAP infrastructures
Bug #1102358 reported by
Jose Castro Leon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
Undecided
|
Jose Castro Leon | ||
Bug Description
When using existing LDAP infrastructure, the query retrieves much more information than needed in keystone.
It is extremely expensive when using AD as a backend (you receive much more useless information than the strictly required for keystone to run).
The main idea is sending the attributes in the ldap query so the server only replies the attributes needed.
| Changed in keystone: | |
| assignee: | nobody → Jose Castro Leon (jose-castro-leon) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to keystone (master) | #1 |
| Changed in keystone: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to keystone (master) | #2 |
| Changed in keystone: | |
| status: | In Progress → Fix Committed |
| Changed in keystone: | |
| milestone: | none → grizzly-3 |
| status: | Fix Committed → Fix Released |
| Changed in keystone: | |
| milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/