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

ASF GitHub Bot commented on USERGRID-1353:
------------------------------------------

GitHub user keyurkarnik opened a pull request:

    https://github.com/apache/usergrid/pull/618

    Fixed shiro cache to ensure 1:1 mapping between token and principal

    Before this, if a user had multiple sessions with different tokens,
    only one Principal was stored in the cache, with the first token. Now
    every user session has a principal mapped to it in the cache
    
    https://issues.apache.org/jira/browse/USERGRID-1353?filter=-1

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/keyurkarnik/usergrid master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/usergrid/pull/618.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 #618
    
----
commit 8b7aa27d8d08d1009d3d6e83ab6a85b300d8a31b
Author: Keyur Karnik <keyur.karnik+github@...>
Date:   2018-12-18T12:05:32Z

    Fixed shiro cache to ensure 1:1 mapping between token and principal
    Before this, if a user had multiple sessions with different tokens,
    only one Principal was stored in the cache, with the first token. Now
    every user session has a principal mapped to it in the cache

----


> Shiro cache tokens are not synced with Cassandra 
> -------------------------------------------------
>
>                 Key: USERGRID-1353
>                 URL: https://issues.apache.org/jira/browse/USERGRID-1353
>             Project: Usergrid
>          Issue Type: Improvement
>          Components: Stack
>            Reporter: Keyur Karnik
>            Assignee: Keyur Karnik
>            Priority: Major
>
> When there are multiple logins, cassandra tokens and shiro cache tokens get 
> out of sync.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to