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] Rebecca M. Fountain Applications Developer Tacoma Community College Information Systems From: Daniel Fisher [mailto:[email protected]] Sent: Tuesday, August 25, 2015 8:15 PM To: [email protected] Subject: Re: [cas-user] CAS 4.0 - LDAPAuth fails for all users after one credentials failure! On Tue, Aug 25, 2015 at 5:34 PM, Fountain, Rebecca <[email protected]<mailto:[email protected]>> wrote: I have configured CAS 4.0 for our environment and currently have it running in development. Authentication works seamlessly UNTIL any one user has a failed attempt at logging in because of bad credentials. After this, all users are locked out for some period of time. Then, after some time the issue resolves itself. Anyone have any idea what may be causing this? Put the org.ldaptive package in debug and see what your logs say. --Daniel Fisher -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[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
