You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2016/12/14 04:24:58 UTC
[jira] [Comment Edited] (MESOS-6739) Authorize v1 GET_CONTAINERS
call
[ https://issues.apache.org/jira/browse/MESOS-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15747216#comment-15747216 ]
Adam B edited comment on MESOS-6739 at 12/14/16 4:24 AM:
---------------------------------------------------------
{code}
commit 982abdb591f87ccf1748a735af4e2a8a84ab4dbe
Author: Alexander Rojas <al...@mesosphere.io>
Date: Tue Dec 13 17:28:12 2016 -0800
Enabled fine grained authorization for the getContainers API Call.
Enables fine grained authorization for the v1 API call `GET_CONTAINERS`.
Review: https://reviews.apache.org/r/54538/
commit 9ec8b5e9256e3001cfbedb17ca6272dfe31db73a
Author: Alexander Rojas <al...@mesosphere.io>
Date: Tue Dec 13 17:01:11 2016 -0800
Added authorization actions VIEW_CONTAINERS and SET_LOG_LEVEL.
Adds the authorization action `VIEW_CONTAINERS` which takes an object
of type `FrameworkInfo` and `ExecutorInfo` and optionally a
`CommandInfo`.
It also adds the authorization action `SET_LOG_LEVEL` which takes no
object.
Includes testing for the ACLs and interface.
Review: https://reviews.apache.org/r/54535/
{code}
was (Author: adam-mesos):
commit 982abdb591f87ccf1748a735af4e2a8a84ab4dbe
Author: Alexander Rojas <al...@mesosphere.io>
Date: Tue Dec 13 17:28:12 2016 -0800
Enabled fine grained authorization for the getContainers API Call.
Enables fine grained authorization for the v1 API call `GET_CONTAINERS`.
Review: https://reviews.apache.org/r/54538/
commit 9ec8b5e9256e3001cfbedb17ca6272dfe31db73a
Author: Alexander Rojas <al...@mesosphere.io>
Date: Tue Dec 13 17:01:11 2016 -0800
Added authorization actions VIEW_CONTAINERS and SET_LOG_LEVEL.
Adds the authorization action `VIEW_CONTAINERS` which takes an object
of type `FrameworkInfo` and `ExecutorInfo` and optionally a
`CommandInfo`.
It also adds the authorization action `SET_LOG_LEVEL` which takes no
object.
Includes testing for the ACLs and interface.
Review: https://reviews.apache.org/r/54535/
> Authorize v1 GET_CONTAINERS call
> --------------------------------
>
> Key: MESOS-6739
> URL: https://issues.apache.org/jira/browse/MESOS-6739
> Project: Mesos
> Issue Type: Bug
> Components: agent, security
> Reporter: Adam B
> Assignee: Alexander Rojas
> Priority: Critical
> Labels: security
> Fix For: 1.2.0
>
>
> We need some kind of authorization for GET_CONTAINERS.
> a. Coarse-grained like we already did for /containers. With this you could say that Alice can GET_CONTAINERS for any/all containers on the cluster, but Bob cannot see any containers' info.
> b. Fine-grained authz like we have for /state and /tasks. With this you could say that Alice can GET_CONTAINERS and see filtered results where user=alice, but Bob can only see filtered results where user=bob. It would be nice to port this to /containers as well if/when we add it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)