[
https://issues.apache.org/jira/browse/IGNITE-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390496#comment-15390496
]
ASF GitHub Bot commented on IGNITE-2344:
----------------------------------------
GitHub user samaitra opened a pull request:
https://github.com/apache/ignite/pull/887
IGNITE-2344 WebSessionFilter doesn't support session ID renewal
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/samaitra/ignite IGNITE-2344
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/887.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #887
----
commit c2e9af35635bd92b07ed992a8b0faaeafbedbf41
Author: samaitra <[email protected]>
Date: 2016-06-04T20:39:20Z
IGNITE-2344 WebSessionFilter doesn't support session ID renewal
commit a966f49fb3e7d3f6f22324095b1a10dfb31a261b
Author: samaitra <[email protected]>
Date: 2016-06-04T21:01:13Z
IGNITE-2344 WebSessionFilter doesn't support session ID renewal
commit 7d005184837b93d8edf55b0fef977efc51b94354
Author: samaitra <[email protected]>
Date: 2016-07-22T18:52:32Z
Merge remote-tracking branch 'upstream/master' into IGNITE-2344
# Conflicts:
#
modules/core/src/test/java/org/apache/ignite/internal/processors/cache/IgniteTxExceptionAbstractSelfTest.java
#
modules/web/src/main/java/org/apache/ignite/cache/websession/WebSessionFilter.java
commit a6e0d56ee78537d5b1964b86d1ea5242e0708b4a
Author: samaitra <[email protected]>
Date: 2016-07-23T03:32:14Z
IGNITE-2344 WebSessionFilter doesn't support session ID renewal
commit 1eaf006987b4b81111140fd68faceb3772fb85b1
Author: samaitra <[email protected]>
Date: 2016-07-23T03:33:44Z
IGNITE-2344 WebSessionFilter doesn't support session ID renewal
----
> WebSessionFilter doesn't support session ID renewal
> ---------------------------------------------------
>
> Key: IGNITE-2344
> URL: https://issues.apache.org/jira/browse/IGNITE-2344
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: ignite-1.4
> Reporter: Denis Magda
> Assignee: Saikat Maitra
>
> It's quite a common scenario to update a session ID after a user successfully
> logged in preserving the session content for further usage.
> Ignite's {{WebSessionFilter}} doesn't support such a use case creating a
> session from scratch.
> To support this behavior we can store a special Cookie that will hold latest
> session ID. When a session is passed to {{WebSessionFilter}} and the filter
> detects that this is a fresh session it will check the Cookie in advance. If
> the Cookie exists and holds an old session ID then the filter will be able to
> get a session content from the cache using the old ID and put it back using
> the new ID.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
