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

Posted to issues@ignite.apache.org by "Denis Garus (Jira)" <ji...@apache.org> on 2020/10/13 10:21:00 UTC

[jira] [Updated] (IGNITE-13112) CacheEvent#subjectId is always null for cache events with types EVT_CACHE_STARTED and EVT_CACHE_STOPPED

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

Denis Garus updated IGNITE-13112:
---------------------------------
    Description: 
For getting the current security context, we have to use the IgniteSecurity interface only. 
We need to get rid of all other ways to transfer a security subject id.

  was:
CacheEvents with types EVT_CACHE_STARTED and EVT_CACHE_STARTED have fieldCacheEvent#subjectId always null. 
CacheEvent#subjectId should be subject id associated with SecuritySubject that trigged the cache event.


> CacheEvent#subjectId is always null for cache events with types EVT_CACHE_STARTED and EVT_CACHE_STOPPED
> -------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-13112
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13112
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache, security
>    Affects Versions: 2.8.1
>            Reporter: Denis Garus
>            Assignee: Denis Garus
>            Priority: Major
>              Labels: iep-41
>          Time Spent: 4h 40m
>  Remaining Estimate: 0h
>
> For getting the current security context, we have to use the IgniteSecurity interface only. 
> We need to get rid of all other ways to transfer a security subject id.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)