Problem with WebAdmin authentication when rebuilding Kolab with slapadd.

[Bernhard Reiter]

Am Mittwoch, 18. Januar 2006 16:23 schrieb Adam Tworkowski:
> I am attempting to rebuild a Kolab server from 2.0 to 2.0.3 using by:
>
> -copying user mailboxes
> -restoring mailbox database with /kolab/bin/ctl_mboxlist and
> cyrreconstruct
> -using slapadd to recreate OpenLDAP database
>
> >From a fresh Kolab install, I am then deleting the new OpenLDAP database
>
> in /kolab/var/openldap/openldap-data and attempting to repopulate the
> LDAP database with slapadd.
>
> The imported LDAP database seems sane but I am having issues
> authenticating to the WebAdmin page.  The error is:
>
> "Could not bind to LDAP server: Invalid credentials"
>
> I am finding authentication errors in the apache-error logs.  I suspect
> that it is related to php_pw in kolab.conf and the the password for
> nobody in LDAP being out of sync.

> That said, I have attempted to change nobody's passwd with
> kolabpasswd.  It is failing on the first step as I do not have the
> existing passwd for nobody (do I?).  The passwd for nobody in the LDAP
> database looks hashed and doesn't seem to work.

Usually kolab.conf will have the cleartext password for nobody.
You can use this to to just set it in the LDAP.
To change the ldap, you need to have write permissions,
which manager has.
Look into the kolab_bootstrap how to create a password entry
that can be stored in the LDAP.
 
> Am I looking in the right direction to resolve this issue?  

Yes, I think so.

> The reason I 
> am attempting to do a full rebuild -- only migrating mail, sieve and
> ldap data -- is because I suffered a major issue with Cyrus's POP3 last
> week in which POP3 service irrecoverably died. 

This sounds strange as there should be a reason why pop3 died
and does not come back.


> I restored from recent 
> backup and only needed to restore the day's mail since LDAP was
> up-to-date.
>
> Jan 10 11:44:38 mail <debug> master[30676]: about to
> exec /kolab/bin/pop3d
> Jan 10 11:44:38 mail <error> master[6351]: process 30675 exited,
> signaled to death by 25
> Jan 10 11:44:38 mail <warning> master[6351]: service pop3s pid 30675 in
> READY state: terminated abnormally
> [ X 1000s... ]