Probably this is an old question but I could not find an answer by surfing the
web.
With CAS 3.0 I can reproduce this sequence of events:
-An user logs in any of our applications through CAS.
-His password is changed in the LDAP server.
-The user can now log in by using both the new password and the old password.
With the old password CAS does not even bind to the LDAP server with the
username.
After CAS is restarted, the user can log in only with the new password.
How can we avoid these logins with the old password without restarting CAS?
Thanks in advance
This is a relevant part of deployerConfigContext.xml file:
ldap://ldap.xxxx.yyy.com:389/
java.naming.security.authentication
simple
TERRA
-->
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas
