Hi ,
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"
event when an update is triggered by the jdbc thin client, contains the uuid
of the node that executed the update rather than the logged in jdbc thin
client user.
If this is a limitation with the current version of ignite, is there any
workaround to get this information ?
This was discussed in the 'Ignite users' group
http://apache-ignite-users.70518.x6.nabble.com/JDBC-thin-client-incorrect-security-context-td31354.html
And I was advised to continue my conversation here.
Andrei mentions that the uuid associated with the event should be that of
the jdbc client( in our case the logged in dbeaver user ). But I notice that
the event always contains the uuid of the node where the query gets executed
.
I do manage to get the right jdbc client from the authenticationcontext in
the authorize and form the right securitycontext. But this doesnt reflect in
the generated cacheevent.
Kindly guide.
regards,
Veena.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
