[
https://issues.apache.org/jira/browse/IGNITE-5077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982761#comment-15982761
]
ASF GitHub Bot commented on IGNITE-5077:
----------------------------------------
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/1870
IGNITE-5077 - Support service security permissions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5077
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1870.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1870
----
commit a19938d1fdce87ccaa5b1262921f7281348bffca
Author: dkarachentsev <[email protected]>
Date: 2017-04-25T11:53:48Z
IGNITE-5077 - Support service security permissions
----
> Support service security permissions
> ------------------------------------
>
> Key: IGNITE-5077
> URL: https://issues.apache.org/jira/browse/IGNITE-5077
> Project: Ignite
> Issue Type: New Feature
> Components: managed services
> Reporter: Dmitry Karachentsev
> Assignee: Dmitry Karachentsev
> Fix For: 2.1
>
>
> Need to add capability to specify permissions to allow/disallow executions of
> particular services (similar to compute tasks).
> The following permissions should be added to the SecurityPermission enum:
> SERVICE_DEPLOY - for IgniteServices.deployXXX methods.
> SERVICE_CANCEL - for IgniteServices.cancel and IgniteServices.cancelAll
> methods.
> SERVICE_INVOKE - for IgniteServices.service, IgniteServices.services and
> IgniteServices.serviceProxy methods.
> SERVICE_INVOKE should allow fine-grained authorization based on service name,
> similar to TASK_EXECUTE. E.g., a particular user should be able to execute
> service A, but not service B.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
