On Mon, Aug 31, 2015 at 2:26 PM, Fountain, Rebecca <[email protected]> wrote:
> Hi Daniel, > > > > I had done that, but wasn’t able to make much sense of the errors. After > throwing the bad credentials error, all attempts to authenticate by any > user get the following error: > > > > 2015-08-25 13:45:25,293 DEBUG > > [org.ldaptive.provider.jndi.NamingExceptionUtils] - naming exception class > javax.naming.NamingException is ambiguous, > > maps to multiple result codes: [OPERATIONS_ERROR, ALIAS_PROBLEM, > ALIAS_DEREFERENCING_PROBLEM, LOOP_DETECT, AFFECTS_MULTIPLE_DSAS, OTHER] > That's a debug message, not the error. Posting an entire authentication event would be helpful. However, looking over your config I see at least one problem. You should not use the same connection pool for both DN resolution and binding. Configure separate pools or you're likely to run into access control issues. http://jasig.github.io/cas/4.0.x/installation/LDAP-Authentication.html#ldap_requiring_authenticated_search --Daniel Fisher -- 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
