Hi all,
I have successfully installed CAS and use MS Active Directory as user
database (LDAP handler). We have several AD servers (replicated) so I've
tried to add them into the CAS LDAP handler config, to see if the first
fails what will be the behavior.
Ex: /opt/tomcat/webapps/cas/WEB-INF/deployerConfigContext.xml
...
<bean id="contextSourceEU"
class="org.jasig.cas.adaptors.ldap.util.AuthenticatedLdapContextSource">
<property name="urls">
<list>
<value>ldap://euces01.eu.company.com/</value> IP: 172.16.1.1
<value>ldap://euces02.eu.company.com/</value> IP: 172.16.1.2
</list>
</property>
...
I did two tests:
1) If I manually update /etc/hosts and set euces01.eu.company.com =
172.16.1.3 (instead of 172.16.1.1) and 172.16.1.3 is a running server,
CAS switch successfully to euces02.eu.company.com (172.16.1.2) and I can
authenticate normally. In this case, the switch works fine.
2) If I manually update /etc/hosts and set euces01.eu.company.com =
172.16.1.4 (instead of 172.16.1.1) and 172.16.1.4 is not used (ie no
running server with this IP), then CAS is not switching to the second AD
server. I have waited for 3 min and stop the test.
Is this normal? Is there a timeout config somewhere that controls this
switch if the first LDAP server is down?
Thanks,
Chris
_______________________________________________
Yale CAS mailing list
cas@...
http://tp.its.yale.edu/mailman/listinfo/cas
