Re: Load-balancing LDAP using GSSAPI/Kerberos/Cryus-SASL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


With OpenLDAP you solve this by using an ssl cert with Alternative names on each server – and you use the sasl-host parameter to tell OpenLDAP to use that common name between the various certs on the actual LDAP servers.  How you duplicate that in AD is left to the reader…

Frank Swasey
Systems Architecture & Administration

From: Cyrus-sasl <> on behalf of Tadashi Inayama via Cyrus-sasl <cyrus-sasl@xxxxxxxxxxxxxxxxxxxx>
Reply-To: Tadashi Inayama <tci@xxxxxxx>
Date: Friday, February 12, 2016 at 5:10 PM
To: "cyrus-sasl@xxxxxxxxxxxxxxxxxxxx" <cyrus-sasl@xxxxxxxxxxxxxxxxxxxx>
Subject: Load-balancing LDAP using GSSAPI/Kerberos/Cryus-SASL


I am new to using GSSAPI/Kerberos/SASL but we got it working for authorization for LDAP queries from RHEL 5.11 and RHEL 6.7 clients against Win2k12 R2 Domain Controllers.

But when we try to load balance the LDAP traffic with F5 LTM (with and as the pool members), ldapsearch via gssapi works half the time, and the other half we get an error that the message is changed mid-stream.  We are guessing that Cyrus-SASL does a reverse dns lookup of the domain controllers as a final check, and if the ip address of the domain controller does not match the hostname of the F5 Virtual Server then the error pops back as message changed mid-stream.  So it work half of the time.

So we did some googling and came across this post:

"There is a work around for this at the GSSAPI layer, which is to tell the server to trust any principal that exists in the service's keytab. Unfortunately, Cyrus SASL doesn't seem to expose a mechanism for doing this, and so the only way to do so is via a code change to the SASL library."

This post was from 2009.  So is there currently a mechanism in Cyrus SASL to trust the principals whose key exists in the krb5.keytab?  Or is there some established method to load balance between two MS Domain Controllers?

(The reason we are trying to load balance the ldap queries is so that when we perform patch or other maintenance work on the individual domain controllers, we don't break the authentication/authorization on the RHEL servers.  Without load balancing, we will need to change the authentication server entries on krb5.conf and sssd.conf in each of the RHEL servers.  And we already have dns, ntp, and kerberos load-balancing using the F5, we just need to get the ldap portion completed.)

Thank you very much,
Tadashi  (Windows Domain Controllers)
      \                          /
       \                        /
        \                      /
         \                    /
 (virtual server on F5 LTM)

Attachment: smime.p7s
Description: S/MIME cryptographic signature

[Index of Archives]     [Info Cyrus]     [Squirrel Mail]     [Linux Media]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux