I have also tried this with CAS 3.4.2.1 and cas-server-support-ldap-pwd-expiration-3.4.2 and it appears to do the same thing.
It still seems like the LDAP error messages aren't making their way up through the application for some reason. -- 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
