extract hardcoded configuration in LDAP backend

Bug #1052111 reported by Jose Castro Leon on 2012-09-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Jose Castro Leon

Bug Description

Some of the backend configuration for LDAP is hardcoded.

1. If the mapping does not fit, you have no way to modify it.
2. It needs an existing dumb user on the LDAP system 'cn=dumb,dc=nonexistent'
3. The attribute ignore parameter is hardcoded in the LDAP module

It also helps in the setup to connect to Active Directory

It comprises some minor bugs previously submitted

As long as the minor bugs are related to each other, it seems a better idea to join all the configuration extraction in only one bug

Changed in keystone:
assignee: nobody → Jose Castro Leon (jose-castro-leon)
status: New → In Progress
description: updated
description: updated
Changed in keystone:
status: In Progress → Fix Committed
Changed in keystone:
status: Fix Committed → In Progress

Reviewed: https://review.openstack.org/13185
Committed: http://github.com/openstack/keystone/commit/a4a97eabb8bde395753de330f76085e69290cdfe
Submitter: Jenkins
Branch: master

commit a4a97eabb8bde395753de330f76085e69290cdfe
Author: Jose Castro Leon <email address hidden>
Date: Tue Oct 16 23:25:03 2012 +0200

    Extract hardcoded configuration in ldap backend (bug 1052111)

    Change-Id: I128b0ccdb32694a4fc2f660e73c367aa8b01f257

Changed in keystone:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2012-11-22
Changed in keystone:
milestone: none → grizzly-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-04-04
Changed in keystone:
milestone: grizzly-1 → 2013.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers