[
https://issues.apache.org/jira/browse/WICKET-2591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790085#action_12790085
]
Juergen Donnerstag commented on WICKET-2591:
--------------------------------------------
What is it what you put into your Cookie(s)? Something that allows you to
identify the user. The only "issue" is the password. You might or not mangle it
into the Cookie. Lets assume the password is not available, than you need to
pass something as password that lets your authenticate() method recognize it's
the cookie and not the password. That's not pretty but possible.
I still don't want to make signin accessible. Any sugesstion on how the
signature of a 2nd authenticate() should look like?
> Allow subclasses of AuthenticatedWebSession to set "signedIn" field
> -------------------------------------------------------------------
>
> Key: WICKET-2591
> URL: https://issues.apache.org/jira/browse/WICKET-2591
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-auth-roles
> Affects Versions: 1.4.3
> Reporter: Marat Radchenko
>
> My app implements "remember me" service by setting cookie in authenticate
> method of custom session that subclasses AuthenticatedWebSession.
> In order to automatically login user if cookie present, i need to set
> "signedIn" field to true when session is created, however it isn't possible
> since "signedIn" is private and no way to set it is available.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
