[
https://issues.apache.org/jira/browse/MESOS-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14200463#comment-14200463
]
Till Toenshoff edited comment on MESOS-2040 at 11/6/14 5:05 PM:
----------------------------------------------------------------
I just discussed the issue with BenH and here is what we would like to propose
instead:
We should stick to the existing way which is to use `-credential as a trigger
for the slave / framework to attempt authentication (now based on the selected
`-authenticatee`). At least we should do so until someone comes up with an
authenticatee module that does not make use of either a principal or a
password. This would mean that there was no need for an additional flag
(despite `-authenticatee`), which is good. The reason why this would still work
for ticket based authentication mechanisms is that those still use a principal
(but no password).
was (Author: tillt):
I just discussed the issue with BenH and here is what we would like to propose
instead:
We should stick to the existing way which is to use "--credential" as a trigger
for the slave / framework to attempt authentication (now based on the selected
"--authenticatee"). At least we should do so until someone comes up with an
authenticatee module that does not make use of either a principal or a
password. This would mean that there was no need for an additional flag
(despite --authenticatee), which is good. The reason why this would still work
for ticket based authentication mechanisms is that those still use a principal
(but no password).
> 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)
