You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Michael Torrie <to...@chem.byu.edu> on 2004/06/30 03:12:30 UTC

Single sign-on for multiple contexts/apps

How would I go about implementing a login that would allow access to
several different tapestry apps?  Is there a global session object of
some kind that can be accessed across servlets (Tapestry apps)?

Thanks.

Michael
-- 
Michael Torrie <to...@chem.byu.edu>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


RE: Single sign-on for multiple contexts/apps

Posted by Michael L Torrie <to...@chem.byu.edu>.
On Wed, 2004-06-30 at 09:40, Ben Mathews wrote:
> Perhaps in this case you would want to have your authentication and
> authorization at a front end web server which serves as a proxy to the web
> apps.  It would add a bit of latency, but would reduce the need to maintain
> a solution in multiple languages.

True.  If only I had all the resources I wanted.  Also, each app still
needs to implement various restrictions and usage levels depending on
who the user is (ie set the "role" appropriated within the container, or
in the php apps).

> 
> Ben Mathews
> Central Point, OR
>  
> 
> 
> -----Original Message-----
> From: Michael L Torrie [mailto:torriem@chem.byu.edu] 
> Sent: Wednesday, June 30, 2004 8:31 AM
> To: Tapestry users
> Subject: Re: Single sign-on for multiple contexts/apps
> 
> 
> On Wed, 2004-06-30 at 08:44, Adam Greene wrote:
> > Did you look at Single Sign On at the Servlet Container level??
> 
> I will do so. 
> 
> It looks, however, like we'll have to take a different route as we
> ultimately need a scheme that can work across all of our web apps, which are
> in php, perl, and java.  I'm thinking some kind of sql-backed session table
> (just to store basic info like the user's id, cryptographic hash).  Then a
> cookie associates the client with that server-side information. Then the app
> proceed.
> 
> Michael
> 
> 
> > 
> > ----- Original Message -----
> > From: "Michael Torrie" <to...@chem.byu.edu>
> > To: "Tapestry users" <ta...@jakarta.apache.org>
> > Sent: Tuesday, June 29, 2004 10:12 PM
> > Subject: Single sign-on for multiple contexts/apps
> > 
> > 
> > > How would I go about implementing a login that would allow access to 
> > > several different tapestry apps?  Is there a global session object 
> > > of some kind that can be accessed across servlets (Tapestry apps)?
> > > 
> > > Thanks.
> > > 
> > > Michael
> > > --
> > > Michael Torrie <to...@chem.byu.edu>
> > > 
> > > --------------------------------------------------------------------
> > > -
> > > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > > 
> > > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
-- 
Michael L Torrie <to...@chem.byu.edu>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


RE: Single sign-on for multiple contexts/apps

Posted by Ben Mathews <bm...@wilcoxassoc.com>.
Perhaps in this case you would want to have your authentication and
authorization at a front end web server which serves as a proxy to the web
apps.  It would add a bit of latency, but would reduce the need to maintain
a solution in multiple languages.

Ben Mathews
Central Point, OR
 


-----Original Message-----
From: Michael L Torrie [mailto:torriem@chem.byu.edu] 
Sent: Wednesday, June 30, 2004 8:31 AM
To: Tapestry users
Subject: Re: Single sign-on for multiple contexts/apps


On Wed, 2004-06-30 at 08:44, Adam Greene wrote:
> Did you look at Single Sign On at the Servlet Container level??

I will do so. 

It looks, however, like we'll have to take a different route as we
ultimately need a scheme that can work across all of our web apps, which are
in php, perl, and java.  I'm thinking some kind of sql-backed session table
(just to store basic info like the user's id, cryptographic hash).  Then a
cookie associates the client with that server-side information. Then the app
proceed.

Michael


> 
> ----- Original Message -----
> From: "Michael Torrie" <to...@chem.byu.edu>
> To: "Tapestry users" <ta...@jakarta.apache.org>
> Sent: Tuesday, June 29, 2004 10:12 PM
> Subject: Single sign-on for multiple contexts/apps
> 
> 
> > How would I go about implementing a login that would allow access to 
> > several different tapestry apps?  Is there a global session object 
> > of some kind that can be accessed across servlets (Tapestry apps)?
> > 
> > Thanks.
> > 
> > Michael
> > --
> > Michael Torrie <to...@chem.byu.edu>
> > 
> > --------------------------------------------------------------------
> > -
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > 
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
-- 
Michael L Torrie <to...@chem.byu.edu>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Single sign-on for multiple contexts/apps

Posted by Michael L Torrie <to...@chem.byu.edu>.
On Wed, 2004-06-30 at 08:44, Adam Greene wrote:
> Did you look at Single Sign On at the Servlet Container level??

I will do so. 

It looks, however, like we'll have to take a different route as we
ultimately need a scheme that can work across all of our web apps, which
are in php, perl, and java.  I'm thinking some kind of sql-backed
session table (just to store basic info like the user's id,
cryptographic hash).  Then a cookie associates the client with that
server-side information. Then the app proceed.

Michael


> 
> ----- Original Message ----- 
> From: "Michael Torrie" <to...@chem.byu.edu>
> To: "Tapestry users" <ta...@jakarta.apache.org>
> Sent: Tuesday, June 29, 2004 10:12 PM
> Subject: Single sign-on for multiple contexts/apps
> 
> 
> > How would I go about implementing a login that would allow access to
> > several different tapestry apps?  Is there a global session object of
> > some kind that can be accessed across servlets (Tapestry apps)?
> > 
> > Thanks.
> > 
> > Michael
> > -- 
> > Michael Torrie <to...@chem.byu.edu>
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> > 
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
-- 
Michael L Torrie <to...@chem.byu.edu>


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org


Re: Single sign-on for multiple contexts/apps

Posted by Adam Greene <ag...@iq-2000.com>.
Did you look at Single Sign On at the Servlet Container level??

----- Original Message ----- 
From: "Michael Torrie" <to...@chem.byu.edu>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Tuesday, June 29, 2004 10:12 PM
Subject: Single sign-on for multiple contexts/apps


> How would I go about implementing a login that would allow access to
> several different tapestry apps?  Is there a global session object of
> some kind that can be accessed across servlets (Tapestry apps)?
> 
> Thanks.
> 
> Michael
> -- 
> Michael Torrie <to...@chem.byu.edu>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org