[jira] [Commented] (OWB-757) Tomcat has Session Fixation Protection, will change sessionId upon login, cause sessionScope lost

["Mark Struberg (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OWB-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553546#comment-13553546 ] 

Mark Struberg commented on OWB-757:
-----------------------------------

Np, a small note:

SessionId rewrite is a security feature from Servlets. Apps often force a new Session on login/logout to not have any left-overs in there.
                
> Tomcat has Session Fixation Protection, will change sessionId upon login, cause sessionScope lost
> -------------------------------------------------------------------------------------------------
>
>                 Key: OWB-757
>                 URL: https://issues.apache.org/jira/browse/OWB-757
>             Project: OpenWebBeans
>          Issue Type: Improvement
>          Components: Context and Scopes
>    Affects Versions: 1.1.6
>            Reporter: chunlinyao
>            Priority: Minor
>
> Tomcat has Session Fixation Protection, upon user login the sessionId will change.
> SessionContextManager track sessionContext by sessionId, which will cause sessionContext not found when sessionId changed.
> Can we put the sessionId in the session. and get it from session failback to session.getId()
> UPDATE:
> Sorry it's not related to SessionContextManager, I am using TomEE , the sessionId is provided by TomEE's 
> CdiAppContextsService

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira