[
https://issues.apache.org/jira/browse/WICKET-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-6310.
-------------------------------------
Resolution: Fixed
Fix Version/s: 8.0.0-M4
It was really a bug in Wicket!
Your test started with `session.signOut()` and this leaded to invalidation of
the session after each request cycle.
So the user has been logged in, then redirected to the HomePage, but after the
redirect the session has been invalidated again and the user has been lost, and
then the authorization strategy declined the instantiation of HomePage because
it is only for USER role.
Thanks for the quickstart!
> Once invalidated the Session will be invalidated on every detach
> ----------------------------------------------------------------
>
> Key: WICKET-6310
> URL: https://issues.apache.org/jira/browse/WICKET-6310
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 8.0.0-M3
> Reporter: Marc G.
> Assignee: Martin Grigorov
> Fix For: 8.0.0-M4
>
> Attachments: spring-security.zip
>
>
> I've created a simple project to show that I've a test which works in Wicket
> 7 but is failing in Wicket 8. Its a simple login form which authenticates a
> user with Spring Security.
> In Wicket 8 the user is redirected to the LoginPage after a succesul login
> without an error. In Wicket 7 the user is redirected to the HomePage as
> expected.
> You can change the version in the maven property section.
> I've tried to debug by myself but I didn't found anything...
> Hint: The test is working in Wicket 8 if you redirect the page with
> setResponsePage(new HomePage.class) instead of setResponsePage(Homepage.class)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
