You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by "Gerhard Petracek (JIRA)" <ji...@apache.org> on 2014/08/17 11:04:18 UTC

[jira] [Resolved] (DELTASPIKE-305) Support @Filters in addition to @Secures

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

Gerhard Petracek resolved DELTASPIKE-305.
-----------------------------------------

    Resolution: Won't Fix

can be done in the method itself.

> Support @Filters in addition to @Secures
> ----------------------------------------
>
>                 Key: DELTASPIKE-305
>                 URL: https://issues.apache.org/jira/browse/DELTASPIKE-305
>             Project: DeltaSpike
>          Issue Type: New Feature
>            Reporter: Arne Limburg
>            Assignee: Arne Limburg
>
> When the result of a method invocation is a Collection it may be desirable not to forbid the complete method call, but just filter the result and remove the objects that the user is not allowed to access.
> Sample business method:
> @CustomSecurityBinding
> public List<Thing> loadThings() {
>     return ...
> }
> Sample authorizer method:
> @Filters @CustomSecurityBinding
> public boolean filter(@SecuredReturn Thing thing) {
>     return thing.isAccessible();
> }



--
This message was sent by Atlassian JIRA
(v6.2#6252)