RE: Re: Re: Authenticator and Component XML configuration

2014-05-15 Thread Sergio
Hi Tim, Thank you very much. It worked like a charm :). It's true, this topic searcher doesn't work, it is almost impossible to find anything. Thanks again, I'll be back soon with new questions. Regards, Sergio -- http://restlet.tigris.org/d

Re: Re: Authenticator and Component XML configuration

2014-05-14 Thread Tim Peierls
I don't think the nested router works the way you expect. You might be able to tweak it to work, but consider creating a separate authenticator (and tracer) instance for each guarded resource. I've written this up several times, but I can never find my old postings when I need them, so I've created

RE: Re: Authenticator and Component XML configuration

2014-05-14 Thread Sergio
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"; W

Re: Re: Authenticator and Component XML configuration

2014-05-14 Thread Tim Peierls
On Wed, May 14, 2014 at 4:46 AM, Sergio 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: Remember that authenti

RE: Re: Authenticator and Component XML configuration

2014-05-14 Thread Sergio
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