Thanks igor, I looked into that and unfortunately the method that controls that is declared final in auth roles' AuthenticatedWebApplication (public final void onUnauthorizedInstantiation(final Component component))
What I came to realize is that by configuring acegi's standard remember-me processing filter, acegi will take care of looking for a cookie and using it to authenticate. The problem seems to be in creating the cookie for the first time, since I don't see how I can use acegi (which traditionally uses authenticationProcessingFilter, that seems to be url driven) to hook into a successful authentication and create the cookie. So my plan to remedy that was to inject the remember me service into the application, and create the cookie after the submission of the login form. I'll experiment with that tomorrow and share my results. But i appreciate the feedback igor.vaynberg wrote: > > this kind of code needs to go into your authorization strategy. there > instead of redirecting to login page you first check for cookies and > if the proper cookie is found simply return true instead of > redirecting to login page. you can use > (webrequest)requestcycle.get().getrequest() to get to cookies. > > -igor > -- View this message in context: http://www.nabble.com/Looking-for-an-example-of-Remember-me-login-functionality-tp20334450p20335335.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]
