You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.The text was updated successfully, but these errors were encountered: