I'm no expert on wicket-auth-roles but coming from the similar swarm securityframework i think a simple flag if a user is logged in is not going to work. Since the framework still needs to know what permissions the user has. Perhaps you could automatically login a user at the session when the session is created? You could do this in the constructor of your custom session or overwrite the newSession() method from Application.
And offcourse then you need a direct link to a page behind the login page, but if you have setup the framework properly the homepage should already be a securepage or contain direct links to secure pages, so this should not be a problem. Maurice On 9/12/07, Michael Day <[EMAIL PROTECTED]> wrote: > Hi, > > I would like to bypass the sign-in screen during development, but > AuthenticatedWebSession provides no setSignedIn() method. So as far > as I can tell, there is no way to skip the sign-in screen... > > Am I missing something? If not, can it be changed? > > Thanks! > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
