Re: Not able to start second server node due to authentication failure

2019-11-13 Thread Maksim Stepachev
Hi, Look at the parent of DataStreamerPermissionCheckTest. This code contains a test implementation of security: org.apache.ignite.internal.processors.security.impl.* ср, 13 нояб. 2019 г. в 15:24, Sankar Ramiah : > Thank you Andei and Zaheer for your response. > > I have tried setting a

Re: Not able to start second server node due to authentication failure

2019-11-13 Thread Sankar Ramiah
Thank you Andei and Zaheer for your response. I have tried setting a security subject with defaultAllowAll true for the server node but there is no change in the output. It is going through authenticateNode of my plugin (that implements GridSecurityProcessor), creates security subject, sets it to

Re: Not able to start second server node due to authentication failure

2019-11-06 Thread Zaheer
Hi Sankar, What Andei said is correct. We need to return a security subject. I faced this problem and solved it like this : *1. Create your own SecurityPermissionSet class that implements org.apache.ignite.plugin.security.SecurityPermissionSet .* /public class TestSecurityPermissionSet

Re: Not able to start second server node due to authentication failure

2019-11-06 Thread Andrei Aleksandrov
Hi, It's correct that SecurityContext is null in your case:     SecurityContext subj = spi.nodeAuth.authenticateNode(node, cred);     if (subj == null) {         // Node has not pass authentication.         LT.warn(log, "Authentication failed [nodeId=" + node.id() +             ", addrs=" +

Not able to start second server node due to authentication failure

2019-11-06 Thread Sankar Ramiah
I have implemented custom authentication and authorization through a plugin. /public class MyPlugin implements GridSecurityProcessor, IgnitePlugin {/ Implemented authenticateNode method which bypasses authentication for server nodes and returns a security context instance. validateNode is