Emulating JServ's session.topleveldomain with Catalina

[Daniel Rall <dl...@finemaltcoding.com>]

Using Tomcat 4.0.1, is there any way to emulate JServ's
session.topleveldomain context configuration?

# Set the domain= header that gets sent with the cookie. This is 
# entirely optional 
# Default: null 
# this is needed when we vhost to avoid multiple login 
session.topleveldomain=.foo.com

I would like all requests to the set of virtual hosts represented by
the glob *.foo.com to share the same session ID.  I was hoping that
org.apache.catalina.authenticator.SingleSignOn would handle this, but
it did not (a new session identifier was assigned each time I visited
a different vhost).

Anyone spare a clue?

                               Thanks,

                             Daniel Rall

--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>

Re: Emulating JServ's session.topleveldomain with Catalina

[Daniel Rall <dl...@finemaltcoding.com>]

Daniel Rall <dl...@finemaltcoding.com> writes:

> Using Tomcat 4.0.1, is there any way to emulate JServ's
> session.topleveldomain context configuration?
>
> # Set the domain= header that gets sent with the cookie. This is 
> # entirely optional 
> # Default: null 
> # this is needed when we vhost to avoid multiple login 
> session.topleveldomain=.foo.com
>
> I would like all requests to the set of virtual hosts represented by
> the glob *.foo.com to share the same session ID.  I was hoping that
> org.apache.catalina.authenticator.SingleSignOn would handle this, but
> it did not (a new session identifier was assigned each time I visited
> a different vhost).

Note: I am not using container-managed security.

--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>