[
https://issues.apache.org/jira/browse/MESOS-5343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376023#comment-15376023
]
Adam B commented on MESOS-5343:
-------------------------------
[~bbannier], Are you still working on this? It'd be nice to pull this into a
1.0-rc3 if we have one, but it's not a release blocker.
Please let me know as soon as there's a RR for me to look at.
> Behavior of custom HTTP authenticators with disabled HTTP authentication is
> inconsistent between master and agent
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-5343
> URL: https://issues.apache.org/jira/browse/MESOS-5343
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Benjamin Bannier
> Assignee: Benjamin Bannier
> Priority: Minor
> Labels: mesosphere, security
>
> When setting a custom authenticator with {{http_authenticators}} and also
> specifying {{authenticate_http=false}} currently agents refuse to start with
> {code}
> A custom HTTP authenticator was specified with the '--http_authenticators'
> flag, but HTTP authentication was not enabled via '--authenticate_http'
> {code}
> Masters on the other hand accept this setting.
> Having differing behavior between master and agents is confusing, and we
> should decide on whether we want to accept these settings or not, and make
> the implementations consistent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)