[
https://issues.apache.org/jira/browse/IGNITE-18910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700129#comment-17700129
]
Ignite TC Bot commented on IGNITE-18910:
----------------------------------------
{panel:title=Branch: [pull/10565/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/10565/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7086733&buildTypeId=IgniteTests24Java8_RunAll]
> Add ability for Ignite Plugins to register their classes as trusted by
> Ignite.
> -------------------------------------------------------------------------------
>
> Key: IGNITE-18910
> URL: https://issues.apache.org/jira/browse/IGNITE-18910
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We are currently skipping security checks for the internal classes (e.g.
> after [IGNITE-15322|https://issues.apache.org/jira/browse/IGNITE-15322] we
> skip authorization of internal tasks.). We recognize internal class as those
> that are located in the security-core.jar.
> We need to provide the ability for Ignite Plugins to declare their own
> classes as Ignite internal classes. It helps to skip unnecessary security
> checks for custom plugin code.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
