HI Andrei, >>IgniteCache<IgniteUuid, SecuritySubject> can help to hold all the information about started transactions and users.
>>Using EventStorageSpi is a good way to handle the events. Thank you . I wanted a review on the below approach : 1.If the cache_put event holds the subject id of the remoteclient, then fetch it using getSpiContext().authenticatedSubject(uuid ) method. ( This in turn will check the AuthenticationContext.context() and match the subjectId in of the event with the one in the AuthenticationContext.context() ) 2.If it holds the subjectId of the node instead of the remoteclient( In this case, the subject returned by point 1 will be null ) - 1.Create a cache( transactionIdToSubjectCache) that holds xid vs security subject information where xid is the id of the transaction started event. The subject Id on this event always holds the remote client id for cache put events generated on dbeaver. 2.When a cacheput event is sent to the storage spi - match the xid as follows a.Get the subject from transactionIdToSubjectCache using the xid. b.If the above is null, get the originating xid of the event xid and get the subject using the originating xid. Is the approach okay ? regards Veena. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
