On Feb 4, 2004, at 8:15 AM, [EMAIL PROTECTED] wrote:
I am using cocoon 2.1 with the authentication framework to build an application that is for both PC and smartphone users. Mobile users should be authenticated automatically through their msisdn which I can get from the http header. I got this to work with an authentication resource that executes the auth-login action and - on success - redirects to the originally requested resource (and otherwise shows the login screen). So far so good - this works fine for http GETs.
That's funny... I implemented the same thing just yesterday (not w/ "msisdn", but same idea, with the authentication resource invoke the auth-login action... just as you describe).
There is one case where an unprotected page does a http POST to a protected page. In this case, I lose the parameters of the POST, I could not find a way to have them forwarded to the redirect-resource of the authentication manager. The documentation says somewhere that it should but it is not visible in the RequestDumperValve traces.
Sorry, I can't help with that (but I'll be watching for the answer...)
BTW, I also noticed that the authentication redirect is a http redirect even if I specify the cocoon: protocol.
I noticed that as well, and wondered about it too. ??
~mark
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
