Well it seems I was taking the wrong approach towards wicket auth roles. Instead of trying to extend it, I took a step back and used the application and the session class as a reference for how to build my own, and I was easily able to acheive the remember me functionality.
I reused the annotation role strategy, but I dropped the dependency on acegi's filter since that generated way more work than is needed for a simple application. And then I was able to use the TokenBasedRememberMeServices (slightly modified and injected into the application) to create and expire the cookies, as well as use acegi's authentication manager to authenticate. I also used my own credentials object that was stored in the session instead of acegi's security context. One last thing to mention, I thought that the best place to auto login was when a new session was created, rather than on an unauthorized instantiation, since its only done once. However I noticed that two sessions were being created at the first hit on the site, so I put in a call to bind() in the session constructor which stopped that from happening. -- View this message in context: http://www.nabble.com/Looking-for-an-example-of-Remember-me-login-functionality-tp20334450p20368700.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
