I figured out that the sign-in panel was storing the authentication data
in a cookie from when we had first tried it before we turned off the
remember-me option and now it's getting it back from there even though
we have turned off that option. Was a simple tweak to fix it.
On 6/28/2011 3:15 PM, sreed wrote:
We are using Jetty which has no session persistence by default. Is it
possible that Wicket is persisting sessions somehow? What else might be
causing this?
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Unwanted-authentication-persistence-tp3631027p3631188.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
