General discussion on installation and configuration of SOGo

Text archives Help


[SOGo] Re: any gotchas on LDAP/AD authentication for upgrading from 1.2.2 to 1.3.0


Chronological Thread 
  • From: "Yu-Phing Ong" < >
  • To: < >, "Yu-Phing Ong" < >
  • Subject: [SOGo] Re: any gotchas on LDAP/AD authentication for upgrading from 1.2.2 to 1.3.0
  • Date: Tue, 31 Aug 2010 12:12:11 +0800
  • Z-usanet-msgid: XID711oHEemL0368X40

I did a reinstall to 1.3.2 nightly, and changed a few things:
SOGoUserSources = (
    {
        CNFieldName = cn; (instead of displayname)
        IDFieldName = sAMAccountName;  (instead of cn)
        IMAPHostFieldName = mailHost;
        UIDFieldName = sAMAccountName;
        baseDN = "dc=test,dc=internal";
        bindDN = "CN=testuser,CN=users,dc=test,dc=internal";
        bindFields = sAMAccountName;
        bindPassword = testpassword;
        canAuthenticate = YES;
        displayName = "Active Directory";
        hostname = "IPAddress";
        id = directory;
        isAddressBook = YES;
        port = 389;
   }

Initially I was hopeful, it was ok and managed to authenticate.

However, after a few minutes, I would start getting Bind errors again:
2010-08-30 12:08:44.319 sogod[3688] Could not bind to the LDAP server 10.x.x.x(389) using the bind DN: CN=Test User,CN=users,DC=test,DC=internal

If I restart sogod, it will work for a while, then start erroring out again.  Strange.

Can anybody help me to shed some light?  I'm almost prepared to go back to 1.2.2 again (assuming I can), since this seems to have been all caused after an upgrade to 1.3.0 and later.

thanks.

------ Original Message ------
Received: 10:45 AM SGT, 08/10/2010
From: "Yu-Phing Ong" < >
To: < >
Subject: any gotchas on LDAP/AD authentication for upgrading from 1.2.2 to 1.3.0


I did an upgrade from 1.2.2 to 1.3.0, and after restarting the service, with the same configuration .GNUstepDefaults that has been working fine, I now get unable to bind errors in /var/log/sogod/sogo.log file, for the bindDN user that I have been using fine for the last year or so.

System is a VM (ESXi 4.0 U2) running Centos 5.5, just did a yum update, using  as the repo:
[sogo-nightly-rhel5]
name=Inverse SOGo nightly-build Repository
baseurl=http://inverse.ca/downloads/SOGo/RHEL5/nightly/$basearch
gpgcheck=0

Did see the "known" error about memcached:
memcached-1.4.2-1.el5.i386 from installed has depsolving problems
  --> Missing Dependency: libevent-1.1a.so.1 is needed by package memcached-1.4.2-1.el5.i386 (installed)

But I don't think this is related.

Using an LDAP browser like jxplorer, I am able to connect to the window AD tree with that bindDN and password, so I know it's not a problem with the bindDN and bindPassword/bindFields.

FYI my SOGoUserSources looks something like this (sanitized):

SOGoUserSources = (
    {
        CNFieldName = displayname;
        IDFieldName = cn;
        IMAPHostFieldName = mailHost;
        UIDFieldName = sAMAccountName;
        baseDN = "dc=test,dc=internal";
        bindDN = " ";
        bindFields = sAMAccountName;
        bindPassword = testpassword;
        canAuthenticate = YES;
        displayName = "Active Directory";
        hostname = "IPAddress";
        id = directory;
        isAddressBook = YES;
        port = 389;
   }
)

Since I am running this in a VM, I had taken a snapshot before, so did a rollback to 1.2.2, and everything is fine again.  So must be something related to the 1.3.0 update.

Any idea what went wrong?  Or have others done the update without any problems?

Thanks.






  • [SOGo] Re: any gotchas on LDAP/AD authentication for upgrading from 1.2.2 to 1.3.0, Yu-Phing Ong, 08/31/2010

Archive powered by MHonArc 2.6.16.

Top of page