Re: Session ID persistence between applications
Re: Session ID persistence between applications
- Subject: Re: Session ID persistence between applications
- From: Chuck Hill <email@hidden>
- Date: Wed, 4 Feb 2009 09:55:05 -0800
On Feb 4, 2009, at 9:06 AM, Sherry Tirko wrote:
Hi All,
Another question about sessions. I store the session ids in cookies.
I was hoping when going from one application to another, I could
keep the same session id. When I hand-off to the second application
a new session is created. Is there a way to use the same session id
between the two applications? Once the 2 initial session are
created, I don't create any more sessions. I'm just hoping I can
create only one session.
You can't. Sessions don't migrate between applications. In fact,
they don't even migrate between instances of the same application. If
you create a session on one instance, and that instance stops, that
session can't be used anymore.
It is possible to add code to allow the sessions to migrate, but it is
not trivial. If you are looking for single sign on (as opposed to
true single session creation), that is somewhat easier. If you can
use something like UM.Cosign or WebAuth (both of which require
Kerberos or some other backing authentication), then integration can
be as easy as looking for the REMOTE_USER header in the first request.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden