You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Michael Park (JIRA)" <ji...@apache.org> on 2017/10/24 01:05:00 UTC

[jira] [Created] (MESOS-8126) Consider decoupling the authorization logic from response creation.

Michael Park created MESOS-8126:
-----------------------------------

             Summary: Consider decoupling the authorization logic from response creation.
                 Key: MESOS-8126
                 URL: https://issues.apache.org/jira/browse/MESOS-8126
             Project: Mesos
          Issue Type: Task
            Reporter: Michael Park


Currently the {{createAgentResponse}} function performs some authorization,
given an optional {{rolesAcceptor}}. {{_getAgents}} function uses this helper
*with* a {{rolesAcceptor}}. {{createAgentAdded}} on the other hand uses the
helper *without* a {{rolesAcceptor}} and is passed to {{Master::Subscriber::send}}
for authorization post-hoc.

From first glance, it seemed like there were 2 authorizations being done for no
reason, and it seems like it could be beneficial to actually pull the authorization
logic out of the response creation logic, rather than coupling them and by-passing
authorization when we want a *custom* authorization logic.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)