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

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

{panel:title=Branch: [pull/12131/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/12131/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8474008&buildTypeId=IgniteTests24Java8_RunAll]

> Initialize no-op security processor for StandaloneGridKernalContext
> -------------------------------------------------------------------
>
>                 Key: IGNITE-25628
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25628
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Mikhail Petrov
>            Priority: Minor
>              Labels: ise
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> All code that performs security checks assumes that security processor is not 
> null even if security is disabled (in this case NoOpIgniteSecurityProcessor 
> is used). Lets initialize NoOpIgniteSecurityProcessor as the security 
> processor for StandaloneGridKernalContext to avoid NPEs when working with 
> StandaloneGridKernalContext.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to