Thanks for the info.. I'm going to mess around with my testing servers more next week. I should have read the top of that page you linked to earlier. It describes the pooling aspect. Pat
On Fri, Oct 9, 2009 at 2:42 PM, Marvin Addison <[email protected]>wrote: > > specified multiple servers but not the pooled option. Would the ldap > > library still attempt the other servers in a round robin fasion? > > Yes. Specifying multiple URLs for the JNDI Context.PROVIDER_URL > property will cause each server to be contacted in round-robin fashion > regardless of the pooling property value. Note this is behavior is > provided by the Sun JNDI implementation and would be available to > _any_ Java LDAP library that uses JNDI under the hood, which is all of > them as far as I know. > > > Something else I should probably mention. I found I got errors when > using > > the full DN for the user. When I used the AD style [email protected], the > > errors went away. > > I don't believe which LDAP authentication handler you're using, Bind > or FastBind. Were these bind errors indicating failed auth attempts > you believe should have been successful? > > > I'm curious if > > it had to do with having some spaces in some of our OU names. > > I believe I've tested CAS LDAP handlers against AD with an OU > containing a space and it worked fine, so I would be surprised if > spaces are the cause of problems. Without further information on your > AD topology, I couldn't even guess about other possible causes. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
