[
https://issues.apache.org/jira/browse/WICKET-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov updated WICKET-5012:
------------------------------------
Attachment: AuthorizingRequestMapper.java
A simple example how to do this.
Use it by registering it as root request mapper:
@Override
public void init() {
super.init();
AuthorizingRequestMapper authorizingRequestMapper = new
AuthorizingRequestMapper(getRootRequestMapper());
setRootRequestMapper(authorizingRequestMapper);
}
> Implement authorization for resources
> -------------------------------------
>
> Key: WICKET-5012
> URL: https://issues.apache.org/jira/browse/WICKET-5012
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.5.0
> Reporter: Martin Grigorov
> Fix For: 7.0
>
> Attachments: AuthorizingRequestMapper.java
>
>
> Currently org.apache.wicket.authorization.IAuthorizationStrategy is focused
> only on Components.
> There is no way to secure an IResource mounted with
> WebApplication#mountResource(ResourceReference) or implicitly at
> /wicket/resource/com.example.MyComponent/some.res
> The API cannot be changed before Wicket 7. Until then applications can use
> custom root request mapper/handler to accomplish the same.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
