ent: Tuesday, March 25, 2008 3:37 PM
> > To: users@wicket.apache.org
> > Subject: Re: Wicket-Security Back Button and Login more than once
> >
> >
> > Logging off using WaspSession.logoff should by default invalidate the
> > session which would erase the user
Sent: Tuesday, March 25, 2008 3:37 PM
> To: users@wicket.apache.org
> Subject: Re: Wicket-Security Back Button and Login more than once
>
>
> Logging off using WaspSession.logoff should by default invalidate the
> session which would erase the user credentials of the ne
see any reason why I should not do this?
>
>
> > -Original Message-
> > From: Maurice Marrink [mailto:[EMAIL PROTECTED]
>
>
> > Sent: Tuesday, March 25, 2008 2:19 PM
> > To: users@wicket.apache.org
> > Subject: Re: Wicket-Security Back Button and Lo
arrink [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 25, 2008 2:19 PM
> To: users@wicket.apache.org
> Subject: Re: Wicket-Security Back Button and Login more than once
>
>
> I checked to be sure :)
> we check it in the constructor:
> // prevent double logins
> if (isUser
rch 25, 2008 1:24 PM
> > To: users@wicket.apache.org
> > Subject: Re: Wicket-Security Back Button and Login more than once
> >
> >
> > Well, we do it by also keeping a reference to the user (not the
> > subject that swarm uses) in the session.
> > And we check
ice Marrink [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 25, 2008 1:24 PM
> To: users@wicket.apache.org
> Subject: Re: Wicket-Security Back Button and Login more than once
>
>
> Well, we do it by also keeping a reference to the user (not the
> subject that swarm uses) in the se
ot;).setLoginContext(context);
> ...
> }
>
> How would you suggest figuring out if it is the same user or not?
>
>
>
>
> > -Original Message-
> > From: Maurice Marrink [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, March 25, 2008 1
ser or not?
> -Original Message-
> From: Maurice Marrink [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 25, 2008 10:02 AM
> To: users@wicket.apache.org
> Subject: Re: Wicket-Security Back Button and Login more than once
>
>
> We also use a "screensaver" but it does n
We also use a "screensaver" but it does not use the login routines,
instead it just verifies the user input against the username and
password from the loggedin user.
Also you can a check on the loginpage to determine if there is already
a logged in user, if there is and it is the same username you
How do you deal with the situation where a user uses the browser back button
and ends up on a login page and then trys to login again? In other words,
how do you allow a user to login more than once. I am also running into this
same situation when I manually throw a
RestartResponseAtInterceptPageEx
10 matches
Mail list logo