All password errors return the same authentication failed exception in CAS, so to the user it looks like they've mis-typed their password. I wrote a CAS extension to provide user feedback on locked/expired/disabled accounts - (http://www.ja-sig.org/wiki/display/CASUM/LDAP+Password+Policy+Enforcement ) I haven't had a chance to update it for CAS 3.4 yet though, so it only works with 3.3.5 right now.
-Eric 2010/5/6 José Miguel Parrella Romero <[email protected]> > José Miguel Parrella Romero escribió: > > I'm trying to define two beans for BindLdapAuthenticationHandler but the > > expected behaviour (falling back to the second bean) is not working for > > me, these are my beans in deployerConfigContext.xml: > > My bad. It's working. The problem is that the LDAP server is rejecting > some of my test users because of password policy, and CAS silently shows > a 'CAS unavailable' message. > > It's important though that neither in the logs or in the login form a > message shows up, is it planned to have specific semantics/error > messages for LDAP errors or what is needed to get that inside CAS? > > Keep up the good work, > > -- > José Miguel Parrella Romero (bureado.com.ve) PGP: 0×88D4B7DF > Debian Developer Caracas, VE/Quito, EC > > -- > 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 > -- Eric Pierce Identity Management Architect Information Technology University of South Florida (813) 974-8868 -- [email protected] -- 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
