Re: [Openstack] New schema for LDAP + Keystone Grizzly?

2013-04-17 Thread spzala
Hi Marcelo, There is an open bug for a similar problem. I have found a workaround that, you need to create an entry manually for default domain in your tree under the new dn (ou=Domains) you have created. Something like, dn: cn=default,ou=Domains,dc=openstack,dc=org objectClass: groupOfNames

Re: [Openstack] New schema for LDAP + Keystone Grizzly?

2013-04-10 Thread Brad Topol
elo Mariano Miziara To: openstack@lists.launchpad.net Date: 04/04/2013 09:07 AM Subject: [Openstack] New schema for LDAP + Keystone Grizzly? Sent by:openstack-bounces+btopol=us.ibm@lists.launchpad.net Hello to all! Before the release of version grizzly 3, the suggested sch

[Openstack] New schema for LDAP + Keystone Grizzly?

2013-04-04 Thread Marcelo Mariano Miziara
Hello to all!Before the release of version grizzly 3, the suggested schema in the openstack documentation (http://docs.openstack.org/trunk/openstack-compute/admin/content/configuring-keystone-for-ldap-backend.html) worked fine. This is the suggested schema:dn: cn=openstack,cn=org dc: openstack obj