Its most likely an issue with your JVM or you backing store. If you're using connection pooling, try disabling it and see if that makes any difference.
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Fri, Nov 28, 2008 at 5:29 AM, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: > 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 > > > > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
