On Tue, 30 Jul 2002, Michael Remijan wrote:
> Date: Tue, 30 Jul 2002 15:46:43 -0500
> From: Michael Remijan <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: RE: Native OS authentication using single sign on ...
>
> I've been following these posts closely because I want to do basically
> the same thing as well. My stupid question is what happens after you
> submit the form?? What I would like to do is create an Object and put
> it in the users session. However, if the user goes click on a link that
> takes them to another webapp, will the object that I put in the session
> still be available?? Single Sign On is great but if I can't passes a
> shared object around via the session (or some other technique) it
> doesn't do me any good.
>
Single sign on avoids the need for a user to authenticate himself or
herself to multiple apps. It does not cause any sharing of sessions -- in
fact, the user will have a separate session for each app that they are
actually using.
Sharing information between webapps is not affected in the slightest by
single sign on's use.
> Mike
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
