Are you using the 2.0 API?
You can subclass the Authenticator and override the authenticate() method.
That gives you access to the Request object, you should then be able to check
the user-agent and do custom authentication.
Authenticator is a filter, so you will have to call setNext() to specify the
next resource in the chain, either an instance of an Authorizer, or your
restlet usually.
-Matt
On Jan 11, 2010, at 9:44 AM, webp...@tigris.org wrote:
Hello,
Given the user-agent property, is it possible to apply different security
scheme's to a given uri?
i.e. when using a browser apply basic or digest security, but when using any
other 'client', use a custom security scheme.
Right now, my authentication is setup once-off in the 'createInboundRoot'
method. But this method is never invoked again after that.
Is there a hook/method i can use to specify which scheme to use based on the
user agent?
Regards,
--KD
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2436294
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2436312