[
https://issues.jboss.org/browse/WFLY-3845?page=com.atlassian.jira.plugin....
]
Sandeep Samdaria commented on WFLY-3845:
----------------------------------------
By "share", I mean that the JSESSIONID doesn't change when I switch my
context in the browser. For e.g. When I visit localhost/abc , I would get
JSESSIONID="ABC123" and when I visit localhost/xyz, I would get the same
JSESSIONID i.e. "ABC123". In jboss-eap-6.2 this is the behavior, but in
wildfly.8.1.0 when I visit localhost/xyz I get a different JSESSIONID "ZYX987"
and when I revisit localhost/abc the previous session is lost and I get a new id.
Share the same jsessionid in different context root
----------------------------------------------------
Key: WFLY-3845
URL:
https://issues.jboss.org/browse/WFLY-3845
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 8.1.0.Final
Environment: Ubuntu 12.04
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Wildfly 8.1.0.Final
Reporter: Sandeep Samdaria
Assignee: Stuart Douglas
I have two applications which need a Single Sign On. User once logged into an application
should not need login again to another application.
To achieve that I was storing the session id in the cookie. The other application used to
retrieve the session and verify the user.
Now, the problem that I am facing, after upgrading to wildfly, is that the each
application is producing different jsessionid. I have also tried the workaround mentioned
in
https://issues.jboss.org/browse/WFLY-3617, but in vain.
I have deployed the same wars in jboss-eap-6.2 and that worked for me.
I have copied the two war over here
https://www.dropbox.com/sh/cq5p373wasn5svj/AACyZaBMBCGaNMaBU8zbW82Za?dl=0
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)