Hello!
Please refer to this specific ticket:
https://issues.apache.org/jira/browse/IGNITE-9560
As well as this Javadoc of the new class:
/**
* Ignite Security Processor.
*
* The differences between {@code IgniteSecurity} and {@code
GridSecurityProcessor} are:
*
* {@code IgniteSecurity} allows to define a current security context by
* {@link #withContext(SecurityContext)} or {@link #withContext(UUID)} methods.
* {@code IgniteSecurity} doesn't require to pass {@code
SecurityContext} to authorize operations.
* {@code IgniteSecurity} doesn't extend {@code GridProcessor} interface
* sequentially it doesn't have any methods of the lifecycle of {@code
GridProcessor}.
*
*/
Regards,
--
Ilya Kasnacheev
пт, 20 нояб. 2020 г. в 19:26, Vishwas Bm :
> Hi,
>
> We were using 2.7.6 and had implemented a custom security plugin for
> authorization and authentication by implementing GridSecurityProcessor.
>
> Now in 2.9 we see that a new interface is provided IgniteSecurity.
> May I know what is the difference between the interfaces, as both look
> similar and what is appropriate place to implement them.
>
> Also in 2.7.6 there was a class called SecurityContextHolder to hold the
> context.
> Now in 2.9 we do not see that class and we see a class
> OperartionClassContext.
> How do we use this new class when using a custom security plugin?
>
>
>
> Regards,
> Vishwas
>
