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

[jira] [Issue Comment Deleted] (MESOS-5709) Authorization for /roles

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

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

(was: www.rtat.net)

> Authorization for /roles
> ------------------------
>
>                 Key: MESOS-5709
>                 URL: https://issues.apache.org/jira/browse/MESOS-5709
>             Project: Mesos
>          Issue Type: Task
>          Components: security
>            Reporter: Adam B
>            Assignee: Jörg Schad
>            Priority: Blocker
>              Labels: mesosphere, security
>             Fix For: 1.0.0
>
>
> The /roles endpoint exposes the list of all roles and their weights, as well as the list of all frameworkIds registered with each role. This is a superset of the information exposed on GET /weights, which we already protect. We should protect the data in /roles the same way.
> - Should we reuse VIEW_FRAMEWORK with role (from /state)?
> - Should we add a new VIEW_ROLE and adapt GET_WEIGHTS to use it?



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