Hi Rémi, I have added your suggestion to the RFE mentioned by Stephan: "Refactor authentication and authorization" http://restlet.tigris.org/issues/show_bug.cgi?id=505 Do you have examples in mind where it would be nice to authorize unauthenticated client requests ? Best regards, Jérôme Louvel -- Restlet ~ Founder and Lead developer ~ <http://www.restlet.org/> http://www.restlet.org Noelios Technologies ~ Co-founder ~ <http://www.noelios.com/> http://www.noelios.com
_____ De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Rémi Dewitte Envoyé : vendredi 14 novembre 2008 23:27 À : [email protected] Objet : Re: Guard suggestion It would also let the autorize() method to decide whether AuthenticationMissing forbids the response or not. For a resource, authorized clients might have more details for example. Rémi On Fri, Nov 14, 2008 at 21:17, Stephan Koops <[EMAIL PROTECTED]> wrote: Hi Rémi, You mean, that a client can authorize himself, but it is not required? I think this is a good ideas. For browser applications I don't now, if browsers could work with this. The authentication should be reworked in the near future (I don't know te current timetable for this). If your proposal is missing then, throw it into the discussion again. best regards Stephan Rémi Dewitte schrieb: Hello all, Let me make a suggestion about the Guard class. It would allow the authorize method to make a decision even if no authentication is present. Why not adding an authorizeMissing attribute and change handling of AUTHENTICATION_MISSING in doHandle method from challenge(response, false); to if(isAuthorizeMissing() && authorize(request)){ accept(request, response); }else{ challenge(response, false); } Cheers, Rémi
