shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Stamer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SHIRO-392) Shiro Extension for JAX-RS Implementation Sun Jersey
Date Mon, 05 Nov 2012 12:20:12 GMT

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

Jan Stamer commented on SHIRO-392:
----------------------------------

Added an implementation at Github https://github.com/PE-INTERNATIONAL/shiro-jersey .
                
> Shiro Extension for JAX-RS Implementation Sun Jersey
> ----------------------------------------------------
>
>                 Key: SHIRO-392
>                 URL: https://issues.apache.org/jira/browse/SHIRO-392
>             Project: Shiro
>          Issue Type: Improvement
>            Reporter: Jan Stamer
>
> We've added an extension to Shiro which enables Shiro annotations in the JAX-RS implementation
Sun Jersey.
> You can do the following with it:
> @Path("/changelog")
> @RequiresPermissions("repository:read")
> public class ChangelogResourceImpl {
>    @POST
>    @Consumes(MediaType.APPLICATION_JSON)
>    @Path("/addObject")
>    @Override
>    @RequiresPermissions("repository:write")
>    public Response addObject(ObjectJson objectJson) {
>       someService.addObject(object);
>       return Response.ok().build();
>    }
> }
> If the user is not authenticated Http Status Code 401 is returned. If the user has insufficient
privileges Status Code 403 is returned.
> Right now we've only added support for the annoation @RequiresPermissions. The other
Shiro annoations could easily be added in the same fashion. Yet currently that's the only
one we need.

--
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

Mime
View raw message