You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Marco Massenzio (JIRA)" <ji...@apache.org> on 2015/10/12 22:46:05 UTC
[jira] [Updated] (MESOS-2949) Design generalized Authorizer
interface
[ https://issues.apache.org/jira/browse/MESOS-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marco Massenzio updated MESOS-2949:
-----------------------------------
Sprint: Mesosphere Sprint 15, Mesosphere Sprint 16, Mesosphere Sprint 17, Mesosphere Sprint 18, Mesosphere Sprint 19, Mesosphere Sprint 20, Mesosphere Sprint 21 (was: Mesosphere Sprint 15, Mesosphere Sprint 16, Mesosphere Sprint 17, Mesosphere Sprint 18, Mesosphere Sprint 19, Mesosphere Sprint 20)
> Design generalized Authorizer interface
> ---------------------------------------
>
> Key: MESOS-2949
> URL: https://issues.apache.org/jira/browse/MESOS-2949
> Project: Mesos
> Issue Type: Task
> Components: master, security
> Reporter: Alexander Rojas
> Assignee: Alexander Rojas
> Labels: acl, mesosphere, security
>
> As mentioned in MESOS-2948 the current {{mesos::Authorizer}} interface is rather inflexible if new _Actions_ or _Objects_ need to be added.
> A new API needs to be designed in a way that allows for arbitrary _Actions_ and _Objects_ to be added to the authorization mechanism without having to recompile mesos.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)