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

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on IGNITE-9861:
----------------------------------------

GitHub user BiryukovVA opened a pull request:

    https://github.com/apache/ignite/pull/4963

    IGNITE-9861: Authorization object names must always be non-null.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/BiryukovVA/ignite IGNITE-9861

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4963.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4963
    
----
commit f97dfaec3baf9d60ae1c0c8683db2e7281533b6a
Author: Vitaliy Biryukov <bi...@...>
Date:   2018-10-11T18:43:53Z

    IGNITE-9861: Authorization object names must always be non-null.

----


> 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.8
>
>
> 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
(v7.6.3#76005)