mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marco Massenzio (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-3560) JSON-based credential files do not work correctly
Date Tue, 06 Oct 2015 19:09:27 GMT

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

Marco Massenzio commented on MESOS-3560:
----------------------------------------

cc: [~adam-mesos]

I think the reasoning behind using a {{bytes}} field instead of a {{string}} was to enable
other modules to use auth secrets, other than just passwords (eg, Tokens, keys, etc.)

At least according to Adam's [MesosCon presentation|https://www.youtube.com/watch?v=G3sn1OLYDOE].

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

Mime
View raw message