[
https://issues.apache.org/jira/browse/MESOS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955799#comment-14955799
]
Michael Park commented on MESOS-3560:
-------------------------------------
{noformat}
commit a21d41f136e5000ea6ac2fbeace738579ce6df55
Author: Isabel Jimenez <[email protected]>
Date: Tue Oct 13 20:26:26 2015 +0200
Changed secret field in V1 `Credential` from `bytes` to `string`
Review: https://reviews.apache.org/r/39099
{noformat}
> JSON-based credential files do not work correctly
> -------------------------------------------------
>
> Key: MESOS-3560
> URL: https://issues.apache.org/jira/browse/MESOS-3560
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Michael Park
> Assignee: Isabel Jimenez
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> Specifying the following credentials file:
> {code}
> {
> “credentials”: [
> {
> “principal”: “user”,
> “secret”: “password”
> }
> ]
> }
> {code}
> Then hitting a master endpoint with:
> {code}
> curl -i -u “user:password” ...
> {code}
> Does not work. This is contrary to the text-based credentials file which
> works:
> {code}
> user password
> {code}
> Currently, the password in a JSON-based credentials file needs to be
> base64-encoded in order for it to work:
> {code}
> {
> “credentials”: [
> {
> “principal”: “user”,
> “secret”: “cGFzc3dvcmQ=”
> }
> ]
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
