You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Bernd Mathiske (JIRA)" <ji...@apache.org> on 2016/05/12 09:56:12 UTC

[jira] [Commented] (MESOS-5212) Allow any principal in ReservationInfo when HTTP authentication is off

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

Bernd Mathiske commented on MESOS-5212:
---------------------------------------

This patch is implementation-only (with tests), which is proper. I am assuming the documentation changes that go along with the new behavior will then be posted against MESOS-5215? IMHO it would also be OK to dedicate limited doc updates to the ticket here.

> Allow any principal in ReservationInfo when HTTP authentication is off
> ----------------------------------------------------------------------
>
>                 Key: MESOS-5212
>                 URL: https://issues.apache.org/jira/browse/MESOS-5212
>             Project: Mesos
>          Issue Type: Improvement
>    Affects Versions: 0.28.1
>            Reporter: Greg Mann
>            Assignee: Greg Mann
>              Labels: mesosphere
>             Fix For: 0.29.0
>
>
> Mesos currently provides no way for operators to pass their principal to HTTP endpoints when HTTP authentication is off. Since we enforce that {{ReservationInfo.principal}} be equal to the operator principal in requests to {{/reserve}}, this means that when HTTP authentication is disabled, the {{ReservationInfo.principal}} field cannot be set.
> To address this in the short-term, we should allow {{ReservationInfo.principal}} to hold any value when HTTP authentication is disabled.



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