Re: DirectAction authentication/redirect
Re: DirectAction authentication/redirect
- Subject: Re: DirectAction authentication/redirect
- From: Chuck Hill <email@hidden>
- Date: Wed, 10 Dec 2003 09:50:40 -0800
One solution is to let the page handle login instead of the DirectAction:
http://wodev.spearway.com/cgi-bin/WebObjects/WODev.woa/wa/Main?wikiPage=HowT
oHandleLogin
You can do a similar thing in the direct action but the page way is more
flexible and prevents unauthenticated access if you later change the access
paths in your app.
As for the session ID, if you are generating the pages containing the
direct actions from WO then the session ID should be provided for you. If
you are moving between static HTML and WO generated pages then about the
only solution is to use cookies to store the session ID and instance number.
Chuck
At 04:34 PM 09/12/2003 -0800, Sam Barnum wrote:
>What would be a good strategy for requiring validation on a
>DirectAction, then redirecting the user after login back to the
>directAction URL?
>
>Example:
>http://localhost:51403/cgi-bin/WebObjects/CaseStudy.woa/wa/
>editCase?_id=7
>should redirect to the main authentication page, and set something in
>the session indicating the page to take the user to after
>authentication.
>
>Maintaining the sessionID seems to be the really messy part here.
>
>Thanks for any advice!
>
>-Sam
>_______________________________________________
>webobjects-dev mailing list | email@hidden
>Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
>Do not post admin requests to the list. They will be ignored.
>
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.