Having Several LDAP Hosts in the CMC

[JuanCLazaro]

Hi all,

does anyone know how it is supposed to work when in the LDAP authentication are defined more than one LDAP hosts?

If one the hosts stops working... will the next one available be selected so that the login can keep on working?

Otherwise, anyone knows what is this useful for?

Thanks a lot

[former_member136842 · Accepted solution]

Hello Juan,

yes - that works such as you described.

Regards

-Seb.

[JuanCLazaro · Accepted solution]

Well,

the thing is that it is not working. We are on XIR2 and once the host stops working, no user can log in.

We are not sure if there could be a bug or something.

Thanks for your answer

[former_member136842 · Accepted solution]

Hello Juan,

whcih SP Level do you have ?

REgards

-Seb.

[JuanCLazaro · Accepted solution]

We are on SP5

[former_member136842 · Accepted solution]

check the deployment and configuration guide of rel.2 on page 243. maybe you did something wrong in your configuration.

-Seb.

[JuanCLazaro · Accepted solution]

Hi again,

I have checked the manual and I have seen that It could have something to do with the way the ldap hosts are configured and not the way it is configured in the CMC. I have seen that all ldap hosts must be configured the same way and also that each of them have to refer to the rest.

I'll pass this to the LDAP administrator and see how it is at this moment.

Thanks again

[JuanCLazaro · Accepted solution]

Hi Seb,

I have not configured the referrals part in the authentication: "LDAP Referral Credentials and Maximum Referral Hops", could this have something to do? Or this is for a different purpose...

Thanks

Regards

[former_member136842 · Accepted solution]

Hi Juan,

try to increase this parameter and check again.

Regards

-Seb.

[JuanCLazaro]

I did not find a good solution for this

[BasicTek]

Due to the way our CMS maintains connections to LDAP when you enter multiple LDAP hosts the failover can be around 2 minutes. Try testing each LDAP host directly to verify they all work. Backup the CMS DB before making changes as an incorrect LDAP host could lead to lost groups/users

Other customers have used different solutions like a DNS redirect or LDAP load balancer for faster cut-over times.

Regards,

Tim