You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:27:30 UTC

[jira] [Issue Comment Deleted] (MESOS-6739) Authorize v1 GET_CONTAINERS call

     [ https://issues.apache.org/jira/browse/MESOS-6739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated MESOS-6739:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> 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
(v7.6.3#76005)