Thanks guys for all the replies. I did get it to work - by adding
logic to manually create/update a JSESSIONID cookie with the Domain
set to the parent domain (e.g., company.com).This logic could be
placed into a tomcat valve, or in some other place along the request
control flow. Wanting
Guys,
I am using several sub-domains that all point to the same app (they
cause different content to be displayed, depending on the sub-domain).
For example, I have:
content1.myapp.com
content2.myapp.com
content3.myapp.com
...etc...
I need the session data to be shared across these
the signle sign on valve
could be useful. But valves won't magically make your session datas shared.
Steve Parker a écrit :
Guys,
I am using several sub-domains that all point to the same app (they
cause different content to be displayed, depending on the
sub-domain). For example, I have
