Thank you very much for your answer. I think I would use the classes approach
using the createInboundRoute as in the book.
How about my second question? Can I attach the authenticator to only some of
the methods of my resources? I.e. protect only PUT, POST, and DELETE while
keeping GET public?
On Wed, May 14, 2014 at 4:46 AM, Sergio sertin...@gmail.com wrote:
Can I attach the authenticator to only some of the methods of my
resources? I.e. protect only PUT, POST, and DELETE while keeping GET
public? Maybe using roles?
You can do per-resource or even per-method authorization:
Hi again,
I want to protect some resources under /apps/{appid}:
/apps/{appId}/object
To avoid flooding I have pasted my code here:
http://pastebin.com/gqc2dbFS
I use the tracer filter to print the details of the request. The requested URI
is:
Resource URI : http://localhost:8080/apps/1;
3 matches
Mail list logo
