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.

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

Allow requiring client certificates for HTTP access #2573

Closed
schmichael opened this issue Apr 18, 2017 · 3 comments
Closed

Allow requiring client certificates for HTTP access #2573

schmichael opened this issue Apr 18, 2017 · 3 comments

Comments

@schmichael
Copy link
Member

Currently mutual TLS is only enforced for Nomad's RPC. Users interacting with Nomad's HTTP endpoint do not need to present a client certificate even when all TLS options are enabled on the agent.

A new tls option should be added to allow requiring clients to present a certificate signed by the same CA when communicating with the HTTPS API.

@weargoggles
Copy link
Contributor

does #2608 satisfy this?

@dadgar
Copy link
Contributor

dadgar commented May 9, 2017

It does! Thanks!

@dadgar dadgar closed this as completed May 9, 2017
@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 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants