Description
In the current Ignite security approach security subject id is considered to be a node id (see IgniteSecurityProcessor#withContext()). In the case of thin clients, this approach doesn't work correctly. If some operation is executed on behalf of the thin client on a remote node (node that is different from one to which thin client connection was established), it's impossible in the same way as for a node to obtain a thin client security subject information.
Attachments
Issue Links
- causes
-
IGNITE-12579 JDBC SQL INSERT operation hangs with security enabled.
- Resolved
-
IGNITE-11992 Improvements for new security approach
- Patch Available
- is fixed by
-
IGNITE-12759 Getting a SecurityContext from GridSecurityProcessor
- Resolved
- links to