[
https://issues.apache.org/jira/browse/MESOS-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200083#comment-14200083
]
Till Toenshoff commented on MESOS-2040:
---------------------------------------
h4. Request for quick discussion
Due to Adam's valuable comment on the above RR, the following issue emerged and
needs to be decided upon;
The existing logic on enabling a slave to attempt authentication is purely
based on the existence of a credential. While that served its purpose, things
now become a little odd when adding new authenticatees supporting
authentication without credentials (think e.g. ticket based authentication
schemes).
Seems we got at least two options for enabling the attempt of authentication
from the slave side;
- add an explicit `--authenticate` flag to the slave
- use the new `--authenticatee` selector (introduced by the above RR) and
authenticate only if a viable one (non empty?) was given
> Authenticatee Module: Integrate authenticatee module in slave
> -------------------------------------------------------------
>
> Key: MESOS-2040
> URL: https://issues.apache.org/jira/browse/MESOS-2040
> Project: Mesos
> Issue Type: Improvement
> Reporter: Till Toenshoff
> Assignee: Till Toenshoff
>
> Allow for slave authentication via authenticatee module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
