Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Thu, 23 Jun 2016 12:31:16 +0000 (UTC)
From: "Adam B (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12957141.1460103574000.9275.1466685076206@Atlassian.JIRA>
In-Reply-To: <JIRA.12957141.1460103574000@Atlassian.JIRA>
References: <JIRA.12957141.1460103574000@Atlassian.JIRA> <JIRA.12957141.1460103574894@arcas>
Subject: [jira] [Commented] (MESOS-5150) Authorize Agent HTTP Endpoints
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 23 Jun 2016 12:31:18 -0000


    [ https://issues.apache.org/jira/browse/MESOS-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346339#comment-15346339 ] 

Adam B commented on MESOS-5150:
-------------------------------

Missed one: /state was only being filtered on the master.
https://reviews.apache.org/r/49082/

> Authorize Agent HTTP Endpoints
> ------------------------------
>
>                 Key: MESOS-5150
>                 URL: https://issues.apache.org/jira/browse/MESOS-5150
>             Project: Mesos
>          Issue Type: Epic
>          Components: security, slave
>            Reporter: Adam B
>            Assignee: Alexander Rojas
>              Labels: agent, authorization, mesosphere, security, slave
>             Fix For: 1.0.0
>
>
> As we add authentication in agent http endpoint handlers in MESOS-4847, we now have the opportunity to perform ACL-based authorization on these endpoints.
> Most important is the authorization of the /files endpoints, as those allow access to executor sandboxes (and agent logs), and the operator may wish to control which users may access which sandboxes.
> Similarly, the operator may only want certain users to be able to view agent flags, change logging level, enable the profiler, etc.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)