[jboss-jira] [JBoss JIRA] (WFLY-3845) Share the same jsessionid in different context root

[Claudio Miranda (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001552#comment-13001552 ] 

Claudio Miranda commented on WFLY-3845:
---------------------------------------

The session-config must be on web.xml. Tested with wildfly 8.1 and the JSESSIONID is added to the / context.
Also if you want SSO, you must enable SSO on undertow subsystem, it adds a JSESSIONIDSSO to the / path automatically, that is another topic.

{code}
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">

    <session-config>
        <session-timeout>1</session-timeout>
        <cookie-config>
            <path>/</path>
        </cookie-config>
    </session-config>

</web-app>
{code}

> 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)