Re: Review for IGNITE-13112 The current security context should be obtained using the IgniteSecurity interface only.

Maksim, ok. Let me know if you have any questions. ср, 21 апр. 2021 г. в 17:51, Maksim Stepachev : > Please wait. I'm watching your review. > > вт, 6 апр. 2021 г. в 20:14, Denis Garus : > > > Hello, Igniters! > > > > I've raised the PR [1] for the issue [2]. > > Could somebody review it? > > >

Re: Review for IGNITE-13112 The current security context should be obtained using the IgniteSecurity interface only.

Please wait. I'm watching your review. вт, 6 апр. 2021 г. в 20:14, Denis Garus : > Hello, Igniters! > > I've raised the PR [1] for the issue [2]. > Could somebody review it? > > Suggested implementation > > If Ignite Security (IS) is enabled, then executors, accessed through the > PoolProcessor,

Review for IGNITE-13112 The current security context should be obtained using the IgniteSecurity interface only.

Hello, Igniters! I've raised the PR [1] for the issue [2]. Could somebody review it? Suggested implementation If Ignite Security (IS) is enabled, then executors, accessed through the PoolProcessor, are wrapped to a security-aware implementation. Security-aware implementation sets proper