thanks for the input guys..

I have to admit at this point, setting this up under FreeBSD was a breeze compared to what is going on now.

I have made 3 attempts at this today.. twice on CentOS 5.4 and once on Ubuntu 10 Server.

Given the differences in platform with identical outcomes I am thinking that it _has_ to be something with my slapd.conf file.

I am still getting error 49s even if I use the actual word secret as the pass.

Nov 2 19:02:00 ldap2 slapd[15768]: conn=0 fd=11 ACCEPT from IP=127.0.0.1:44448 (IP=0.0.0.0:389) Nov 2 19:02:00 ldap2 slapd[15768]: conn=0 op=0 BIND dn="cn=Manager,dc=acadaca,dc=net" method=128 Nov 2 19:02:00 ldap2 slapd[15768]: conn=0 op=0 RESULT tag=97 err=49 text= Nov 2 19:02:00 ldap2 slapd[15768]: conn=0 fd=11 closed (connection lost)

And this is how my ldap.conf is setup

BASE dc=acadaca,dc=net HOST localhost

I would appreciate it greatly if someone could please give it a look.

Thank you

On Tue, Nov 2, 2010 at 6:35 PM, Quanah Gibson-Mount quanah@zimbra.com wrote:

--On Tuesday, November 02, 2010 11:07 PM +0100 Benjamin Griese der.darude@gmail.com wrote:

...

Hello Tim,

the "password" you supply won't work, as it is not encoded in base64.

Try to generate a password hash + base64-enc with "slappasswd" and set this string as your password hash for rootpw. http://linux.die.net/man/8/slappasswd

Benjamin,

There is no requirement that the password value for the rootpw entry in slapd.conf be SSHA hashed or Base 64 encoded.

I.e.,

rootpw  secret

is perfectly valid.

Also, an LDIF file with

userPassword: secret

is also perfectly valid, as either slapadd or slapd (via ldapadd) will take care of encoding it to Base64.

--Quanah

--

Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc

---

Zimbra ::  the leader in open source messaging and collaboration