Yeah,you can use @RolesAllowed.  The OAuth implementation just sets the 
appropriate principal and principal-role mappings.  The servlet, JAX-RS, 
or EJB layer does the rest.

On 4/15/2013 2:36 PM, Doug Schnelzer wrote:
> In the oauth2 skeleton key example their was just one role ("user")
> specified for the database-services REST services.  Is it easy to
> protect some services with one role (say using the role "customer" for
> the CustomerService) and another required role for other services (say
> using the role "products" for the ProductService)?  Can I use the
> @RolesAllowed annotation?
>
> Thanks for the help
>
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
>
>
>
> _______________________________________________
> Resteasy-users mailing list
> Resteasy-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/resteasy-users
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Resteasy-users mailing list
Resteasy-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/resteasy-users

Reply via email to