[
https://issues.apache.org/jira/browse/MESOS-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14594997#comment-14594997
]
Adam B commented on MESOS-2608:
-------------------------------
commit b3a3d53377304de361393de6af9ab7e239a4b1bb
Author: Till Toenshoff <[email protected]>
Date: Sun Jun 21 08:23:37 2015 +0000
Added secret check to CRAM-MD5 authenticatee.
Updating authenticatee to check for secret within credential. Adding a
test verifying immediate authenticatee failure when secret is missing.
Review: https://reviews.apache.org/r/33057
> test-framework should support principal only credential
> --------------------------------------------------------
>
> Key: MESOS-2608
> URL: https://issues.apache.org/jira/browse/MESOS-2608
> Project: Mesos
> Issue Type: Improvement
> Reporter: Till Toenshoff
> Assignee: Till Toenshoff
> Priority: Minor
> Labels: mesosphere
> Fix For: 0.23.0
>
>
> Currently the test-framework is enforcing a secret to be present within the
> supplied credential (via environment variable {{DEFAULT_SECRET}}).
> This is not an ideal example on how framework developers should approach
> authentication.
> The presence check for the password has to be done within the authenticatee
> (-module) implementation itself, if needed.
> {{secret}} is typed {{optional bytes}} within the {{Credential}} proto
> message and should be handled accordingly by the framework to allow for
> password free (e.g. credential cache based) authentication.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
