> On v3.5.1, I get a big Java stack trace error: > > 2012-10-25 10:26:21,408 ERROR > [org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler] - [LDAP: error > code 49 - Invalid Credentials]; nested exception is > javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid > Credentials]
Confirmed. I haven't had a chance to investigate, but I noted the change in behavior immediately after our deployment. This behavior is unacceptable from a sysadmin perspective. Authentication failures are not exceptional and it's become substantially more difficult to sort signal from noise from all the stack traces in the logs now. I'd appreciate your filing a Jira issue and I'll fix it. 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
