<html><body><div><br></div><div><br></div>LdapLoginModule sufficient with multiple ldap urls:<div><br></div><div><span style="color:rgb(59,35,34);font-family:Courier;font-size:14px;background-color:rgba(215,211,183,0.85)"> ldapUrl="ldap://adua02.ua.... ldap://<a href="http://adua03.ua">adua03.ua</a>….”</span><br></div><div><br></div><div>and timeouts</div><div><br></div><div><p style="margin:0px;font-stretch:normal;font-size:14px;line-height:normal;font-family:Courier;color:rgb(59,35,34);background-color:rgba(215,211,183,0.85)"><span style="font-variant-ligatures:no-common-ligatures"> connectTimeout="1500"</span></p>
<p style="margin:0px;font-stretch:normal;font-size:14px;line-height:normal;font-family:Courier;color:rgb(59,35,34);background-color:rgba(215,211,183,0.85)"><span style="font-variant-ligatures:no-common-ligatures"> resultTimeout="3000"</span></p></div><div><span style="font-variant-ligatures:no-common-ligatures"><br></span></div><div>The module as a whole fails and returns failed authentication as soon as the connectTimeout period; </div><div>it does not appear that the failed initial connection triggers attempting the second ldap server.</div><div><br></div><div><i>Is there a straightforward config in jaas.config that will try the next ldap server if the first times out?</i></div><div><br></div><div>For reasons beyond my ken or control, connections to our ldap (AD) servers are failing frequently today.</div><div><br></div><div>David</div></body></html>