[
https://issues.apache.org/jira/browse/IGNITE-12759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085720#comment-17085720
]
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 *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5227881&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
> Fix For: 2.8.1
>
> Time Spent: 2h
> 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:
> # Try to get a security context using _ClusterNode_ attributes (as it works
> now);
> # Get a security context through _GridSecurityProcessor_.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
