[ https://issues.apache.org/jira/browse/MESOS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945607#comment-14945607 ]
Marco Massenzio edited comment on MESOS-3560 at 10/6/15 7:17 PM: ----------------------------------------------------------------- BTW - the approach of just documenting the fact that the string needs to be base64-encoded seems to me the easiest, let's just document it (maybe adding a suggestion to use {{openss base64}} utility to encode/decode). was (Author: marco-mesos): BTW - this approach seems to me the easiest, let's just document it (maybe adding a suggestion to use {{openss base64}} utility to encode/decode). > 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)