When keystone is configured to set up an LDAP server to use as
it's identity backend, the creation of the root DN fails. The
problem is that one of the mods in the modify operation that sets
up the root DN is incorrect, which causes the entire modify
operation to fail. The incorrect mod is attempting to configure
some attribute indexes, but one of the attributes it specifies is
undefined. This patch removes the undefined attribute from the
template that is used to create the modify operation.
Change-Id: I413587130c64ca4f5f467b2ea1c0ab12867999ce
Closes-Bug: 1275158
* Build the base DN from a given domain name
* Remove all hard-coded names to allow configuration of base DN
* Fix manager DN (cn=Manager,dc=...)
* Add ldap init_ldap()
* Add support for clean.sh
Change-Id: Ieb69be9740653645b8e000574ad3fe59a0f97540
Domain entries are no longer stored in keystone ldap.
Removing the creation from devstack ldap install
Fixes Bug 1194204
Change-Id: I9c93d3021cc2bb058d1ef57bebcf3a13dc5bdd34
This update sets the ou value for groups to be the new keystone
ldap default of UserGroups
Fixes Bug1191807
Change-Id: I9b7383100045155ca35b04190f42be641a0c6ea8
Fixes Bug1144927
This fix adds a Domain subtree to the initial
LDAP structure for configuring keystone's LDAP.
Change-Id: I6ec06efc9e0a40bfc81d838b9f0d6167e9441dff
Addressed reviewers comments and added some extra properties
needed by latest version of keystone.
This fix sets some needed values in keystone.conf to ensure
that keystone can add entries to LDAP and remain schema
compliant. It creates a new special role (_member_) that
is needed by the latest version of keystone and also
fixes tenant_id to be tenantId.
Change-Id: Ia2a1ebb7cbedb0af106c74aa9181843cc9739f5d