You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Valentin Kulichenko (JIRA)" <ji...@apache.org> on 2017/04/11 20:52:41 UTC

[jira] [Resolved] (IGNITE-4948) Web session clustering fails to work with Spring Security

     [ https://issues.apache.org/jira/browse/IGNITE-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Valentin Kulichenko resolved IGNITE-4948.
-----------------------------------------
    Resolution: Fixed

> Web session clustering fails to work with Spring Security
> ---------------------------------------------------------
>
>                 Key: IGNITE-4948
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4948
>             Project: Ignite
>          Issue Type: Bug
>          Components: websession
>    Affects Versions: 1.9
>            Reporter: Valentin Kulichenko
>            Assignee: Valentin Kulichenko
>             Fix For: 2.0
>
>
> {{WebSessionFilter.doFilterV2}} method do not refresh the local instance of session after {{chain.doFilter}}. But it's possible that session is replaced by some other filter (e.g. due to login). And if after this replacement some attributes are added, they do not end up in cache.
> dev@ list discussion: http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-2741-spring-session-design-td14560.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)