Re: Wicket-Security Back Button and Login more than once

2008-03-26 Thread Maurice Marrink
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 (isUserLoggedIn()) { throw new RestartResponseException(HomePage.class

Re: Wicket-Security Back Button and Login more than once

2008-03-25 Thread Maurice Marrink
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

RE: Wicket-Security Back Button and Login more than once

2008-03-25 Thread Warren
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 not use the login routines, instead it just verifies

Re: Wicket-Security Back Button and Login more than once

2008-03-25 Thread Maurice Marrink
out if it is the same user 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

RE: Wicket-Security Back Button and Login more than once

2008-03-25 Thread Warren
:[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 session. And we check if the the user

Re: Wicket-Security Back Button and Login more than once

2008-03-25 Thread Maurice Marrink
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 not use the login routines, instead it just verifies the user input against

RE: Wicket-Security Back Button and Login more than once

2008-03-25 Thread Warren
:[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 (isUserLoggedIn()) { throw new

Re: Wicket-Security Back Button and Login more than once

2008-03-25 Thread Maurice Marrink
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 Login more than once I checked to be sure :) we check it in the constructor: // prevent double logins

RE: Wicket-Security Back Button and Login more than once

2008-03-25 Thread Warren
, 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 new user. But i am not sure what modifications you made