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

Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/03 10:56:00 UTC

[jira] [Commented] (IGNITE-9861) Authorization object names must always be non-null.

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

Maxim Muzafarov commented on IGNITE-9861:
-----------------------------------------

[~VitaliyB] [~garus.d.g]

Is this issue still actual?

> Authorization object names must always be non-null.
> ---------------------------------------------------
>
>                 Key: IGNITE-9861
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9861
>             Project: Ignite
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 2.6
>            Reporter: Vitaliy Biryukov
>            Assignee: Vitaliy Biryukov
>            Priority: Major
>             Fix For: 2.9
>
>
> Currently, sometimes *null* name parameter passing to a method *GridSecurityProcessor:authorize*. This leads to the fact that it is impossible to determine the authorization object by authorization event.



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