Greetings all,
I've only just recently learned about configuring and using LDAP using slapd.conf configuration. Recently, however, I have been asked to configure LDAP on a server running Red Hat Enterprise Linux 6. I've run into a few problems.
First of all, when I try to connect via LDAP Browser/Editor to view the cn=config list, it connects but gives me Error 32 - No Such Object. The following is the the cfg file that Ldap Browser/Editor uses to connect to the session:
################################# # # # LDAP Browser v2.8 config file # # # # cn=config all attributes # # # #################################
host=[my server's IP address] port=389 sslport=636 basedn=cn=config version=3 managerdn=cn=Manager,cn=config managerlogin=no autoconnect=no leafindicatortype=int leafindicator=numsubordinates managereferrals=no supportsmovetree=no derefaliases=never sorttree=ascending ldap.attributes.list=* +
The managerdn i got from the olcRootDN line in olcDatabase={2}bdb.ldif file. And the rest i got from zytrax.com online book ( http://www.zytrax.com/books/ldap/ch14/cn=config.cfg )
My question is, is there any other configuration or any other additional steps that I need to take after yum install in order to make this LDAP server functional? What have I missed? Any help will be much appreciated!
Thank you.
--On Monday, June 11, 2012 9:59 AM -0400 Roger Martinez roger.martinez.87@gmail.com wrote:
Greetings all,
I've only just recently learned about configuring and using LDAP using slapd.conf configuration. Recently, however, I have been asked to configure LDAP on a server running Red Hat Enterprise Linux 6. I've run into a few problems.
First of all, when I try to connect via LDAP Browser/Editor to view the cn=config list, it connects but gives me Error 32 - No Such Object. The following is the the cfg file that Ldap Browser/Editor uses to connect to the session:
################################# # # # LDAP Browser v2.8 config file # # # # cn=config all attributes # # # #################################
host=[my server's IP address] port=389 sslport=636 basedn=cn=config version=3 managerdn=cn=Manager,cn=config managerlogin=no autoconnect=no leafindicatortype=int leafindicator=numsubordinates managereferrals=no supportsmovetree=no derefaliases=never sorttree=ascending ldap.attributes.list=* +
The managerdn i got from the olcRootDN line in olcDatabase={2}bdb.ldif file. And the rest i got from zytrax.com online book (http://www.zytrax.com/books/ldap/ch14/cn=config.cfg%C2%A0)
My question is, is there any other configuration or any other additional steps that I need to take after yum install in order to make this LDAP server functional? What have I missed? Any help will be much appreciated!
You need to use the rootdn for the cn=config DB, not the bdb database rootdn. Zytrax's information is highly unreliable, I would avoid using their documentation for anything.
I would first get binding as the cn=config db's rootdn working via ldapsearch before trying to use a browser. Most ldap browsers also do not understand cn=config. Apache Directory Studio would be an exception.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
Nice, JXplorer did the trick. I've managed to add all my organization's schemas. Now I'm having trouble figuring out how to start adding entries (pretty much an address book).
In {2}bdb under config I've defined my olcRootDN (uid=root,dc=incnet,dc=net), olcRootPW, and olcSuffix (dc=incnet,dc=net).
It accepts these changes. Then I try to connect to this DN:
Base DN: dc=incnet,dc=net User DN: uid=root,dc=incnet,dc=net Password: [mypassword]
It authenticates but says "unable to list." Details read:
javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'dc=incnet,dc=net'
I apologize if these are elementary issues! Can anyone help me and tell me where I'm going wrong this time?
On Mon, Jun 11, 2012 at 2:30 PM, Nick Milas nick@eurobjects.com wrote:
On 11/6/2012 8:59 μμ, Quanah Gibson-Mount wrote:
Most ldap browsers also do not understand cn=config. Apache Directory
Studio would be an exception.
JXplorer works fine!
Nick
openldap-technical@openldap.org
-
Nick Milas -
Quanah Gibson-Mount -
Roger Martinez