Re: Issue with custom security plugin and thin clients

Hello! I afraid these changes will not be included in the 2.10 version. сб, 19 дек. 2020 г. в 06:03, Vishwas Bm : > Hi Denis, > > Thanks for the feedback. > > I had also put a comment in one of your PR regarding iep-41. > https://github.com/apache/ignite/pull/8038#issuecomment-742230009 > > > It

Re: Issue with custom security plugin and thin clients

Hi Denis, Thanks for the feedback. I had also put a comment in one of your PR regarding iep-41. https://github.com/apache/ignite/pull/8038#issuecomment-742230009 It will be great if you can provide input on this. Regards, Vishwas On Fri, 18 Dec, 2020, 21:39 Denis Garus, wrote: > Hi! > I do

Re: Issue with custom security plugin and thin clients

Hi! I don't understand why you do something related to thin clients inside onDisconnected method? The rest looks good to me. ср, 9 дек. 2020 г. в 17:00, vbm : > Hi Denis, > > Any thoughts on the approach mentioned above ? > > > Regards, > Vishwas > > > > -- > Sent from: http://apache-ignite-devel

Re: Issue with custom security plugin and thin clients

Hi Denis, Any thoughts on the approach mentioned above ? Regards, Vishwas -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Issue with custom security plugin and thin clients

Hi Denis, Thanks for the suggestion. I was trying to implement the approach of using the cache to store the thin clients security context. Below is the approach, I wanted to follow: 1) Add the thin client secCtx to cache during authentication time. 2) Retrieve the thin client secCtx using subjId

Re: Issue with custom security plugin and thin clients

Hi! Node attributes can't be used to spread a thin client's security context. For this purpose, you can use a cache of Ignite, a third-party database, or other tools appropriate to your case. сб, 28 нояб. 2020 г. в 06:16, Vishwas Bm : > Hi Denis, > > > Thanks for the reply. > Yes I was looking

Re: Issue with custom security plugin and thin clients

Hi Denis, Thanks for the reply. Yes I was looking for a way to spread the security context to all cluster nodes when a thin client(sqlline) gets authenticated. I tried to see if I can use node attributes or user attributes to pass the information to other nodes. When a cluster of ignite server is

Re: Issue with custom security plugin and thin clients

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