You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2020/03/17 17:50:00 UTC

[jira] [Commented] (IGNITE-12759) Getting a SecurityContext from GridSecurityProcessor

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

Ignite TC Bot commented on IGNITE-12759:
----------------------------------------

{panel:title=Branch: [pull/7523/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5134102&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Getting a SecurityContext from GridSecurityProcessor
> ----------------------------------------------------
>
>                 Key: IGNITE-12759
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12759
>             Project: Ignite
>          Issue Type: Improvement
>          Components: security
>            Reporter: Denis Garus
>            Assignee: Denis Garus
>            Priority: Major
>              Labels: iep-41
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Extend the _GridSecurityProcessor_ interface by adding _securityContext(UUID subjId)_ method and use this method to get the actual security context.
> h4. Backward compatibility
> The logic of getting security context for Ignite:
>  # Get a security context through _GridSecurityProcessor_;
>  # If _GridSecurityProcessor_ returned null, try to get a security context using _ClusterNode_ attributes (as it works now).



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