fixes #1289 - Trim \n at the end of a secret when using Mesos auth#1290
fixes #1289 - Trim \n at the end of a secret when using Mesos auth#1290
Conversation
|
I think when we implemented this in #710 we intentionally read all of the bytes in the file. This is because the authentication mechanism in Mesos could be an arbitrary module. This change would make it impossible to define a secret that ends in the byte Maybe we could benefit from a second opinion from people who have worked on authentication in Mesos. cc: @adam-mesos |
|
Interesting points. Mesos' default CRAM-MD5 authentication must assume the secret does not include a newline character, since the master's --credentials file is newline-delimited between credentials. Kerberos authentication does not use the secret, since keytabs/tickets are managed out of band. Other alternative authenticatee modules may want to include newlines in their secrets, so for their sake we may want to read the entire file, but until they complain we can probably trim any newlines when reading the secret file. Perhaps in the future, it could be up to the CRAM-MD5 authenticatee to trim out newlines. |
|
@drexin soo sorry for bothering you on this. I seemed to miss deleting trailing space on secret file....
|
|
Thanks @everpeace |
|
@drexin @everpeace @ConnorDoyle @adam-mesos I am seeing the 'Master refused authentication' while authenticating Marathon against Mesos Master. Here is the info. Thoughts? Here is the Mesos Master setting Here is the marathon configuration Here is the list of packages Version: |
No description provided.