You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2013/06/17 11:33:20 UTC

[jira] [Commented] (WICKET-5012) Implement authorization for resources

    [ https://issues.apache.org/jira/browse/WICKET-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685400#comment-13685400 ] 

Martin Grigorov commented on WICKET-5012:
-----------------------------------------

A possible solution for this problem can be found in branch '5012-authorize-resources'.
The diff can be seen at: https://git-wip-us.apache.org/repos/asf/wicket/repo?p=wicket.git;a=commitdiff;h=88b5d5cb482bc7bb22e2ceb9503e5056b0e89572

Any comments are welcome!
                
> 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.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