You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Greg Mann (JIRA)" <ji...@apache.org> on 2016/03/21 23:47:25 UTC
[jira] [Commented] (MESOS-4951) Enable actors to pass an
authentication realm to libprocess
[ https://issues.apache.org/jira/browse/MESOS-4951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205317#comment-15205317 ]
Greg Mann commented on MESOS-4951:
----------------------------------
After some discussion with [~bmahler], we settled on the following approach: a parameter can be added to {{process::initialize()}} which sets the authentication realm for libprocess. This allows the master/agent/tests to set the realm at initialization time. Since {{process::initialize()}} is called frequently throughout libprocess, we must also alter the function to return a boolean which indicates whether or not a particular invocation of {{initialize}} was the *first* invocation. This will allow us to assert during startup that we set the authentication realm as desired.
> Enable actors to pass an authentication realm to libprocess
> -----------------------------------------------------------
>
> Key: MESOS-4951
> URL: https://issues.apache.org/jira/browse/MESOS-4951
> Project: Mesos
> Issue Type: Bug
> Components: libprocess, slave
> Reporter: Greg Mann
> Assignee: Greg Mann
> Labels: authentication, http, mesosphere, security
>
> To prepare for MESOS-4902, the Mesos master and agent need a way to pass the desired authentication realm to libprocess. Since some endpoints (like {{/profiler/*}}) get installed in libprocess, the master/agent should be able to specify during initialization what authentication realm the libprocess-level endpoints will be authenticated under.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)