OpenLDAP ldap_bind configuration error: Invalid credentials (49)

I am using Ubuntu 10.4 server and I am trying to configure OpenLDAP as an authentication protocol for SVN and other services. However, I completely do not understand how ldap works, and after installing the config example, I tried to populate it without success. This is mistake:

ldap_bind: Invalid credentials (49) 

This seems to be an example of a configuration problem, or rather, an administrator configuration. However, I tried to change it with a cryptographic password, but did not get any results. Code configuration below

  # Load modules for database type dn: cn=module,cn=config objectclass: olcModuleList cn: module olcModuleLoad: back_bdb.la # Create directory database dn: olcDatabase=bdb,cn=config objectClass: olcDatabaseConfig objectClass: olcBdbConfig olcDatabase: bdb # Domain name (eg home.local) olcSuffix: dc=home,dc=local # Location on system where database is stored olcDbDirectory: /var/lib/ldap # Manager of the database olcRootDN: cn=admin,dc=home,dc=local olcRootPW: admin # Indices in database to speed up searches olcDbIndex: uid pres,eq olcDbIndex: cn,sn,mail pres,eq,approx,sub olcDbIndex: objectClass eq # Allow users to change their own password # Allow anonymous to authenciate against the password # Allow admin to change anyone password olcAccess: to attrs=userPassword by self write by anonymous auth by dn.base="cn=admin,dc=home,dc=local" write by * none # Allow users to change their own record # Allow anyone to read directory olcAccess: to * by self write by dn.base="cn=admin,dc=home,dc=local" write by * read 
+4
source share
1 answer

Have you tried connecting through the CLI?

 ldapsearch -x -D "cn=admin,dc=home,dc=local" -W -h <hostname> 

Check your syslog, slapd logs its output there by default.

You can also use slapcat, which must be run locally to find out if your database was created or not (slapd will break, if not). It will display the first available database. Use the -n flag to extract a specific database:

 slapcat -n <database number> 

My bets are that you are authenticating the wrong database.

+2
source

All Articles