move dumb_member to configuration on LDAP module
Bug #1050398 reported by
Jose Castro Leon
This bug report is a duplicate of:
Bug #1052111: extract hardcoded configuration in LDAP backend.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Committed
|
Medium
|
Jose Castro Leon | ||
Bug Description
LDAP backend needs an existing dumb user on the LDAP system.
This is hardcoded in the LDAP backend pointing to 'cn=dumb,
When the LDAP module tries to validate this user it fails on Active Directory
because it is a non existing user.
| Changed in keystone: | |
| assignee: | nobody → Jose Castro Leon (jose-castro-leon) |
| tags: | added: blueprint ldap-ad |
| Changed in keystone: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in keystone: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to keystone (master) | #1 |
| Changed in keystone: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/