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:37 UTC

[jira] [Issue Comment Deleted] (MESOS-5706) GET_ENDPOINT_WITH_PATH authz doesn't make sense for /flags

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

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

(was: www.rtat.net)

> GET_ENDPOINT_WITH_PATH authz doesn't make sense for /flags
> ----------------------------------------------------------
>
>                 Key: MESOS-5706
>                 URL: https://issues.apache.org/jira/browse/MESOS-5706
>             Project: Mesos
>          Issue Type: Task
>          Components: security
>            Reporter: Adam B
>            Assignee: Alexander Rojas
>            Priority: Major
>              Labels: mesosphere, security
>             Fix For: 1.0.0
>
>
> The master or agent flags are exposed in /state as well as /flags, so any user who wants to disable/control access to the flags likely intends to control access to flags no matter what endpoint exposes them. As such, /flags is a poor candidate for GET_ENDPOINT_WITH_PATH authz, since we care more about protecting the flag data than the specific endpoint path.
> We should remove the GET_ENDPOINT authz from master and agent /flags until we can come up with a better solution, perhaps a first-class VIEW_FLAGS acl.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)