<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 05/08/2012 04:55 PM, Leandro Reox wrote:
<blockquote
cite="mid:CAC9jWxMw2YD1EMSQ7kGx5jA8TGFKGD0mqP-tf7kwj4pN-c6dSA@mail.gmail.com"
type="cite">Hi all
<div><br>
</div>
<div>Is Keystone LDAP integration working, we read that the last
changes to keystone broke the compatibility with ldap. Actually
the import of the keystone schema into openldap is failing.
Anyone knows that actually this is actually broken ? or maybe
were doing something wrong</div>
<div><br>
</div>
<div>Regards<br>
lele</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
Post to : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
More help : <a class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</pre>
</blockquote>
<br>
<br>
The Schema that Keystone expects by default has been changed to use
the defautls ferom the OpenLDAP and or 389 DirSrv, which are the
RFC schemas for users, groups, etc. You can override pretty much
any of the object classes to a different one if you want, but there
is no need to. The custom schema committed to Keystone late last
year is not required nor expected.<br>
<br>
<br>
</body>
</html>