[
https://issues.apache.org/jira/browse/MESOS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941821#comment-14941821
]
Michael Park commented on MESOS-3560:
-------------------------------------
[~ijimenez] Right, our JSON => protobuf parser decodes the input for a
{{bytes}} field. I was thinking the simplest fix would be to base64 encode the
password strings of the JSON input before passing it over to the protobuf
parser, and things will work just fine.
I'm not exactly sure what plans we have going forward, but this seems the
simplest approach to me. What do you think?
> 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.20.0, 0.21.0, 0.22.0, 0.23.0, 0.24.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)
