[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Translating back_ldap config to cn=config format

OK, I used the source (Luke); the old uri config parameter is the LDAP
attribute olcDbURI.  So far, so good;  I have things working to my
eDir backend now.

Now I'm trying to add an AD backend and a little stumped - it expects
the bind username to be in Windows format 'Domain\userName', but slapd
won't let me specify that as an olcDbACLAuthcDN.  I've tried
"Domain\\user" and "Domain\5cUser", but it won't accept anything that
doesn't look like a DN.  So now I'm looking at the acl-bind clause
(olcDbAclBind); what does that look like as an LDAP attribute?

On Tue, Aug 24, 2010 at 1:43 PM, Mark J. Reed <markjreed@gmail.com> wrote:
> To your mailing list welcome.  I here am new...
> I'm trying to configure an LDAP backend, but the man page is still
> slapd.conf-style,  and the mappings to cn=config I've tried aren't
> working.  For instance, to supply the backend LDAP URL, the man page
> lists:
> uri <ldapurl>
> so I tried this:
> olcURI: ldap://foo.bar/
> and got
> Aug 24 13:30:36 bottom slapd[2265]: UNKNOWN attributeDescription
> "OLCURI" inserted.
> Maybe I'm just missing the objectClass that defines those attributes,
> but I don't know what that would be.  I just have olcDatabaseConfig; I
> tried olcLdapConfig, but that wasn't recognized as a legal class name.
>  Where can I find the config schema?
> Any help, pointers to someplace this is actually documented, etc. appreciated.
> Thanks!
> --
> Mark J. Reed <markjreed@gmail.com>

Mark J. Reed <markjreed@gmail.com>