Hello!
If I understood your problem correctly, you need to make a thin client's security context allowed on a remote node. When a security plugin does authenticate a thin client, it should spread the thin client's security context on the cluster. How a security context will be transmitted to a remote node is up to the plugin's developers. Also, you have to implement the GridSecurityProcessor.securityContext(UUID subjId) method, the way this method is used in Ignite can see in the task description [1]. 1. https://issues.apache.org/jira/browse/IGNITE-12759 чт, 26 нояб. 2020 г. в 10:01, Vishwas Bm <bmvish...@gmail.com>: > Hi, > > I was facing an issue with a custom security plugin and thin remote client. > I am using Ignite 2.9.0 version and I am hitting below issue > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-41%3A+Security+Context+of+thin+client+on+remote+nodes > > > I had asked the question in the user listing but unfortunately I did not > get any reply. > So I am posting this question here: > > > http://apache-ignite-users.70518.x6.nabble.com/Query-on-implementing-GridSecurityProcessor-td34672.html > > > *Thanks & Regards,* > > *Vishwas * >
