[WICKET-3991] SignInPanel prevents the page being Stateless when signing in with the "rember me" facility.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5-RC6
• Fix Version/s: 1.5.1
• Component/s: wicket-auth-roles
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Sylvain Vieujot
• Created: 24/Aug/11 16:12
• Updated: 13/Sep/11 08:25
• Resolved: 31/Aug/11 11:14

Description

This worked fine with 1.5-RC5, so I think it is a regression.

Start the webapp ( mvn clean jetty:run )

Log-in with remember me checked.

Stop the webapp

restart it ( mvn clean jetty:run )

The browser should re-log-on and wicket will throw a RuntimeException.
If you refresh the browser, you are properly logged-on.

See the attached quickstart.

Issue Links

• breaks: WICKET-3965 A (stateless) page immediately disappears after the first render
• incorporates: WICKET-4045 Calling wicketTester.clickLink(...) on a StatelessLink causes "PageExpiredException" with Wicket 1.5.0
• is cloned by: WICKET-4010 SignInPanel may lead to infinite redirects if there is rememberMe cookie with outdated data