[
https://issues.apache.org/jira/browse/WICKET-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Pinkham updated WICKET-3493:
--------------------------------
Attachment: RestartResponseAtInterceptPageException.java
It's quite the hack, but it works around the issue for me till more familiar
eyes than mine find time to look at this.
> Login doesn't work if placing the SignInPanel on the HomePage.
> ---------------------------------------------------------------
>
> Key: WICKET-3493
> URL: https://issues.apache.org/jira/browse/WICKET-3493
> Project: Wicket
> Issue Type: Bug
> Components: wicket-auth-roles, wicket-examples
> Affects Versions: 1.5-RC2
> Environment: Ubuntu 10.04 and Wicket 1.5 latest trunk
> Reporter: Ludger Kluitmann
> Assignee: Igor Vaynberg
> Priority: Minor
> Labels: wicket
> Fix For: 1.5-RC3
>
> Attachments: RestartResponseAtInterceptPageException.java, quick1.zip
>
>
> I did some minor changes to wicket example authentication3. I put the
> SignInPanel on the HomePage. The changes look like this:
> HomePage.java
> public HomePage() {
> super();
>
> add(new SignInPanel("signin", true));
> }
> HomePage.html
> <br><br>
> <div wicket:id="signin"></div>
> Now you can see the SignInPanel on the HomePage. If you login you are
> redirected to the home page again. Everything seems to be fine. But if you
> click the Admin Page link you are redirected to the login page. I think you
> should end-up on the Admin Page itself because the login was correct.
> That means also, you cannot use the SignInPanel on your application's home
> page for user login.
> Regards
> Ludger
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
