Hi Rickard, Now that 1.2 M2 is out, I can get to your email!
I would suggest that you try out Restlet 1.2 M2 if you can. The ClientResource class allows you to set the "next" Restlet. If can be a Filter chain leading to the Context#clientDispatcher of your Application or leading to a Client instance. Then, you should develop a special Filter that would enrich the request with the correct credentials. You could even use a Router to handle this on a target URI basis! Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -----Message d'origine----- De : Rickard Öberg [mailto:[email protected]] Envoyé : vendredi 20 mars 2009 03:24 À : [email protected] Objet : How to authenticate to many websites seamlessly? Hi! I want to use the Restlet client in my app along with a notion of Accounts. This means that the user will set up Accounts with logins to a number of websites, and when the application does HTTP requests to those websites the login info should be used automatically. How do I set up Restlet to do this? One way seems to be to subclass Client and override handle(), and on each call check what host is being called, and then add auth info. Is there a better, cleaner way to do it? If so, how? /Rickard ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=13603 02 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1522550
