Re: JDBC thin client incorrect security context

1. Another thing I noticed is that during a update through jdbc client, there could be 2 kinds of threads acting on it. The 'client-connector' thread and the 'sys-stripe'. If the client-connector thread completes the transaction and calls the record on storagemanager, it is able to send a 'cache_pu

Re: JDBC thin client incorrect security context

I hen we tested we saw that older jdbc client would connect without security while latest version would give error and would require the correct username password . Regards Sent from my iPhone > On 17-Feb-2020, at 4:07 AM, VeenaMithare wrote: > > As suggested by you , i have put up this qu

Re: JDBC thin client incorrect security context

As suggested by you , i have put up this question on the 'ignite developers' forum as well. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC thin client incorrect security context

Hi Andrei, I checked again, The uuid associated with the cacheevent is associated to the node that handles the request from the jdbc thin client. It doesnt show the uuid of the logged in jdbc client(DBEAVER user). Do I need to do something to associate the cacheevent with the logged in jdbc clie

Re: JDBC thin client incorrect security context

HI Andrei, That helps..For some reason, i got confused and thought I am getting the UUID of the node on which it is running. thanks, regards, Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC thin client incorrect security context

Hi, I see that you found the ticket related to the current issue: https://issues.apache.org/jira/browse/IGNITE-12589 Looks like it can be a reason of your problem. Generally, I don't know how you implemented your security plugin if you take a look at similar plugin from third party vendor

JDBC thin client incorrect security context

Hi , We have built a security and audit plugin for security of our ignite cluster. We are unable to get the right audit information i.e. we are unable to get the right subject for users logged in through dbeaver ( jdbc thin client. ). This is because the subjectid associated with the "CACHE_PUT"