You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Joerg Schad (JIRA)" <ji...@apache.org> on 2016/07/03 16:46:10 UTC
[jira] [Commented] (MESOS-5709) Authorization for /roles
[ https://issues.apache.org/jira/browse/MESOS-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360603#comment-15360603 ]
Joerg Schad commented on MESOS-5709:
------------------------------------
Refactored /role and getRoles endpoint code.
https://reviews.apache.org/r/49574/
Fixed `delete` usage in authorization_test.cpp.
https://reviews.apache.org/r/49575/
> 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: Joerg 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
(v6.3.4#6332)