Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

nomad address override does not take user:pass in address string #1415

Closed
olenm opened this issue Jul 13, 2016 · 10 comments
Closed

nomad address override does not take user:pass in address string #1415

olenm opened this issue Jul 13, 2016 · 10 comments

Comments

@olenm
Copy link

olenm commented Jul 13, 2016 •
edited
Loading

Nomad version

Nomad v0.4.0

Operating system and Environment details

mac 10.11.5

Issue

we use nomad with an nginx front-end with basic auth and nomad address override does not work with basic auth as presumed with a url address input
(kind of relates to #227)

Reproduction steps

nomad status -address="https://user:[email protected]"

Error querying jobs: Unexpected response code: 401 (<html>
<head><title>401 Authorization Required</title></head>
<body bgcolor="white">
<center><h1>401 Authorization Required</h1></center>
<hr><center>nginx</center>
</body>
</html>
)
olenm added a commit to olenm/nomad that referenced this issue Jul 13, 2016
@olenm
feat(authentication): add basic authentication in address and env-vars (
049df1a 
hashicorp#1415)
@olenm olenm mentioned this issue Jul 13, 2016
Closed
@diptanu
Copy link
Contributor

diptanu commented Jul 15, 2016

@olenm We are going to support end to end TLS between Nomad server, client and the cli which should secure the Nomad cluster.

@diptanu diptanu closed this as completed Jul 15, 2016
@diptanu
Copy link
Contributor

diptanu commented Jul 15, 2016

The end to end TLS is going to land in a month so I am closing this ticket. Please let me know if that would solve your use-case?

@olenm
Copy link
Author

olenm commented Jul 19, 2016 •
edited
Loading

If the TLS implementation includes basic auth in the address-url-param (and/or as env-vars) that would be perfect. (I built locally from PR 1416 and am using it as a work around for the time being)

Thanks for the update!

@BSick7
Copy link

BSick7 commented Aug 17, 2016

@diptanu This was set to land. Any updates as to whether it will be included in 0.4.1?

@dadgar
Copy link
Contributor

dadgar commented Aug 17, 2016

@BSick7 waiting for @olenm to update the PR based on feedback

@BSick7
Copy link

BSick7 commented Aug 17, 2016

@dadgar sorry, I should have been more specific. I was referring to this comment.

The end to end TLS is going to land in a month so I am closing this ticket. Please let me know if that would solve your use-case?

@dadgar
Copy link
Contributor

dadgar commented Aug 17, 2016

@BSick7 Ah! That was never planned for 0.4.x. It will be coming in 0.5.x 👍

@BSick7
Copy link

BSick7 commented Aug 17, 2016

Thanks!

@mlafeldt
Copy link
Contributor

FYI: #1431, which adds support for -address="https://user:[email protected]" is already part of 0.4.0.

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@diptanu @mlafeldt @BSick7 @dadgar @olenm