[jira] [Created] (IGNITE-7779) Ignite fails to start with a custom GridSecurityProcessor and enabled assertions

["Robert Wruck (JIRA)" <ji...@apache.org>]

Robert Wruck created IGNITE-7779:
------------------------------------

             Summary: Ignite fails to start with a custom GridSecurityProcessor and enabled assertions
                 Key: IGNITE-7779
                 URL: https://issues.apache.org/jira/browse/IGNITE-7779
             Project: Ignite
          Issue Type: Bug
          Components: general
    Affects Versions: 2.3
            Reporter: Robert Wruck


When a custom GridSecurityProcessor is installed, ServerImpl.joinTopology will call localAuthentication, which asserts that the passed SecurityCredentials are not null.

Problem 1: There is no good way to set the SecurityCredentials for the local node. The GridGain implementation for example does this by "somehow" obtaining the GridKernalContext and directly setting the magic ATTR_SECURITY_CREDENTIALS attribute.

Problem 2: Whether a GridSecurityProcessor accepts a null SecurityCredentials instance should not be decided in localAuthentication anyway.

Please provide a documented way for GridSecurityProcessors to set set the SecurityCredentials and remove the assertion - it works just fine with null.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)