On 11/04/11 13:29, Bart Coninckx wrote: > Hi all, > > some months ago I posted this problem with the LDAP integration towards > eDirectory: > > > *********************************************************************** > Hi all, > > I'm having problems with a test setup connecting to eDirectory (which > offers LDAP). > > I enabled debugging on the eDirectory side and got this: > > New cleartext connection 0x6f09d00 from 192.168.1.53:1494, monitor = > 0x4130b940, index = 87 > DoBind on connection 0x6f09d00 > Bind name:cn=admin,o=be, version:3, authentication:simple > Sending operation result 0:"":"" to connection 0x6f09d00 > DoSearch on connection 0x6f09d00 > Search request: > base: "" > scope:0 dereference:3 sizelimit:0 timelimit:0 attrsonly:0 > filter: "(objectClass=*)" > attribute: "vendorName" > Sending search result entry "" to connection 0x6f09d00 > Sending operation result 0:"":"" to connection 0x6f09d00 > > > As you can see, the "base" part is empty. > > I tried to edit the openthinclient realm and put in the Secondary Directory: > > ldap://cluster2fs/o=be > > which represents the actual situation. > > For the Readonly Principal I put: > cn=admin,o=be with the correct password. > > I get the impression the bind works perfect, but the first search fails > because of the empty base part. > > Is this production not able to deal with organizations ("o") in stead of > organizational units ("ou") as first level entries in LDAP? > > > thx, > > > Bart > > *********************************************************************** > > > Does anyone have a clue to get behind this issue? > > thx, > > > > Bart > > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > The Open Source Thin Client Solution http://openthinclient.org > openthinclient-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openthinclient-user
I'm, well, err, "proud" to announce that I found the solution, but it was rather silly. I followed the docs for Active Directory, which advises to put the username in a the from of "user@server". For eDirectory this is simply an LDAP FQDN, like cn=admin,ou=company,o=be FYI, B. ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ The Open Source Thin Client Solution http://openthinclient.org openthinclient-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openthinclient-user
