docs: Update Authenticating with HashiCorp Vault for Vault 1.17
-
Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA
What does this MR do and why?
"Authenticating and reading secrets with HashiCorp Vault" (https://docs.gitlab.com/ee/ci/examples/authenticating-with-hashicorp-vault/) needs to be updated.
In Vault 1.17, JWT auth login requires bound audiences on the role when the aud
is set on the JWT.
The bound_audiences
parameter of "jwt" roles must match at least one of the JWT's associated aud
claims. The aud
claim claim can be a single string or a list of strings as per RFC 7519 Section 4.1.3. If the JWT's aud
claim is not set, then the role's bound_audiences
parameter is not required.
https://developer.hashicorp.com/vault/docs/upgrading/upgrade-to-1.17.x#jwt-auth-login-requires-bound-audiences-on-the-role https://developer.hashicorp.com/vault/api-docs/auth/jwt#bound_audiences
- Related to #467795 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.