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 2015/02/24 21:34:05 UTC

[jira] [Resolved] (WICKET-5749) Wicket-auth-roles should deal with resource authorization

     [ https://issues.apache.org/jira/browse/WICKET-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-5749.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 7.0.0-M6

> Wicket-auth-roles should deal with resource authorization
> ---------------------------------------------------------
>
>                 Key: WICKET-5749
>                 URL: https://issues.apache.org/jira/browse/WICKET-5749
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-auth-roles
>    Affects Versions: 7.0.0-M3
>            Reporter: Carl-Eric Menzel
>            Assignee: Carl-Eric Menzel
>            Priority: Minor
>             Fix For: 7.0.0-M6
>
>
> We now have IAuthorizationStrategy.isResourceAuthorized, which is awesome. So far, wicket-auth-roles's implementation allows all resources to go through without any possibility of configuring that.
> I think the default auth strategy shipped with Wicket should support this :-)
> Perhaps an additional annotation like "@AuthorizeResource"?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)