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 <[email protected]> > 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 <[email protected]>wrote: > >> 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 "loginFormPath" value. When it is null, we >> cannot redirect, therefore it calls super#challenge(Response, boolean). >> >> Best regards, >> Thierry Boileau >> >> ------------------------------------------------------ >> >> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3038041 >> > > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3038067
