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

doc: specify ca cert needs to be shared #20620

Merged
merged 3 commits into from
May 17, 2024
Merged

doc: specify ca cert needs to be shared #20620

merged 3 commits into from
May 17, 2024

Conversation

schmichael
Copy link
Member

(Certificate management is the worst.)

Had some confusion from a user thinking they had to use a lb/proxy to configure the Vault integration. I noticed our docs about mTLS/verify_client lacked mentioning that Vault needs to trust Nomad's CA, so I added some words to hopefully make that more clear? The words do not seem like good words so if you have gooder words please suggest them.

@schmichael schmichael added theme/website nomadproject.io infrastructure issues and enhancements backport/website This will backport PR changes to `stable-website` && the latest release-branch labels May 16, 2024
@schmichael schmichael requested review from tgross and jrasell May 16, 2024 21:34
@david-yu
Copy link
Contributor

I'm curious does that mean creating the Vault auth method for nomad with that public CA via the certificate parameter? https://developer.hashicorp.com/vault/docs/auth/cert#configuration

@schmichael
Copy link
Member Author

I'm curious does that mean creating the Vault auth method for nomad with that public CA via the certificate parameter? https://developer.hashicorp.com/vault/docs/auth/cert#configuration

Hm, that certificate parameter is for the certificate auth method, not the JWT auth method. Poking around I think jwks_ca_pem is the parameter people can configure the certificate with?

I'll update the docs to point people to it directly.

@tgross tgross added the stage/needs-rebase This PR needs to be rebased on main before it can be backported to pick up new BPA workflows label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/website This will backport PR changes to `stable-website` && the latest release-branch backport/1.7.x backport to 1.7.x release line stage/needs-rebase This PR needs to be rebased on main before it can be backported to pick up new BPA workflows theme/website nomadproject.io infrastructure issues and enhancements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants