[jira] [Commented] (MESOS-3560) JSON-based credential files do not work correctly

["Sean Owen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069973#comment-15069973 ] 

Sean Owen commented on MESOS-3560:
----------------------------------

This ends up causing a problem in Spark, for later when Mesos gets updated in Spark: https://issues.apache.org/jira/browse/SPARK-12501. Ideally the old field is also supported, but hey.

> 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)