I've fleshed this out, probably in too much detail:
I have a Component made up of several cooperating Applications. There is a
need for common authentication (MyAuthenticator extending
CookieAuthenticator) across all applications. Rather than have each
Application duplicate the login and logout ha
Hi Tim,
yes, you're right, it reverts to the ChallengeAuthenticator behaviour. I
wonder if CookieAuthenticator is really a ChallengeAuthenticator.
Best regards,
Thierry Boileau
2012/12/21 Tim Peierls
> Sounds good, so if you haven't provided a login form, it more or less
> reverts to Challeng
Hi Tim,
I've read your mail, and have a question about this :
>an instance of my CookieAuthenticator extension around a
>Restlet that does nothing. (If you leave out this vacuous Restlet, the
>machinery complains about a Filter with no target.)
Clearly, a filter is meant to transmit the request/r
Sounds good, so if you haven't provided a login form, it more or less
reverts to ChallengeAuthenticator's behavior? (Except the scheme won't be
supported, so it won't actually work, but you'll have some clue as to
what's going on.)
--tim
On Fri, Dec 21, 2012 at 11:57 AM, Thierry Boileau wrote:
>
Hi tim,
I've applied it also on the 2.1 branch.
Best regards,
Thierry Boileau
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3038042
Hello Tim,
I'm sorry for the delay of my answer.
It clearly appears to me that the promised feature were not implemented, and
therefore were lacking from the initial contribution.
Thanks a lot for reporting this issue, I've added your contribution, with a
small adjustement : I test the "loginFor
6 matches
Mail list logo
