Zimbra + External Ldap

[leandrochacha]

Hello

We install a server Zimbra in the Debian Etch. The installation was completed successfully, however do not we obtain to integrate the zimbra with a server ldap external. We utilize the tool Zimbra Administration Console, and we put the IP of the server LDAP external, and to the test of verification that the zimbra does with a user, is deed successfully. However, when we utilize the page of the Zimbra Collaboration Suite, the users created in the LDAP external does not obtain login.

That problem can be due to the filters of research? We are using the uid =%u.

Someone has some suggestion, or indicate some site that explain as configure the zimbra for access a ldap external?

Thank you,

Leandro

[phoenix]

Welcome to the forums.

Does the user you have defined in your external LDAP exist on the Zimbra server? You need to have the user exist on Zimbra as well as the external LDAP. Please also check this wiki article for details about external authentication.

[leandrochacha]

Hi, Bill, thank you very much by the answer.

We follow the steps of the link that you sent, however nevertheless do not we obtain to connect with the user.

If we use the ldapsearch of the debian for do a test:

# ldapsearch -x ldapsearch: /opt/zimbra/cyrus-sasl/lib/libsasl2.so.2: in the version information available (required by ldapsearch) LDAP vendor version mismatch:
library 20340, header 20330

When we utilize the ldapsearch of the zimbra:

#. /ldapsearch -x ldap_bind: Can' t contact LDAP server (-1)

The users exist only by means of the ldap external, where do we add the attributes of the zimbra for they.

Some idea?

Thank you again,

Leandro

[phoenix]

If you need to add a lot of users to Zimbra then you can do a bulk provision, check this wiki article for details.

[quanah]

When we utilize the ldapsearch of the zimbra:

#. /ldapsearch -x ldap_bind: Can' t contact LDAP server (-1)

As noted in the ldapsearch man page, you must specify the host you want to connect to, using either the -h or -H options.

--Quanah

[leandrochacha]

Thank you for reply.
Quanah, when we utilize:

# ldapsearch -h host
LDAP vendor version mismatch: library 20340, header 20330



or:

# ldapsearch -H ldap://192.168.1.83
LDAP vendor version mismatch: library 20340, header 20330


I brought up to date the library of the cyrus-sasl, but still I continue without connect in the ldap. Now, neither the users that are registered in the zimbra are going to connect.

Some idea?


Regards,

Leandro

[quanah]

Yes, use the zimbra ldapsearch. (/opt/zimbra/bin/ldapsearch).

--Quanah

[leandrochacha]

Hello, Quanah


Now I with himself answers with the /opt/zimbra/bin/ldapsearch -x. However, I not with himself connect with the user in the zimbra. The message that appears in the screen of logon is:

The username or password i incorrect. Verify that CAPS LOCK i not on, and then retype the current username and password.

Verifying the log, I have to following message:
Feb 8 16:32:03 paggo-zimbra02 sudo: unable to dlopen /usr/lib/sasl2/libsasldb.so.2: /opt/zimbra/sleepycat/lib/libdb-4.2.so: undefined symbol: pthread_condattr_setpshared
Feb 8 16:32:04 paggo-zimbra02 CRON[20326]: (pam_unix) session closed for user zimbra


Thanks a lot by the help,

[quanah]

Hello, Quanah


Now I with himself answers with the /opt/zimbra/bin/ldapsearch -x. However, I not with himself connect with the user in the zimbra. The message that appears in the screen of logon is:

The username or password i incorrect. Verify that CAPS LOCK i not on, and then retype the current username and password.

Verifying the log, I have to following message:
Feb 8 16:32:03 paggo-zimbra02 sudo: unable to dlopen /usr/lib/sasl2/libsasldb.so.2: /opt/zimbra/sleepycat/lib/libdb-4.2.so: undefined symbol: pthread_condattr_setpshared
Feb 8 16:32:04 paggo-zimbra02 CRON[20326]: (pam_unix) session closed for user zimbra

I bet the zimbra ld.so.conf settings are messing with the system libraries. I'm hoping to get that closed out for the next release: Bug 23254 - Leave /etc/ld.so.conf Alone, Specify Library Paths As Parameters to Compiler/Linker