Support of dynamic OIDC/JWT auth for Hashi Vault #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mksh
force-pushed
the
hashi-vault-oidc-auth
branch
from
872903b to
ee12b20
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for dynamic token acquire via OID Connect auth, and refresh for Hashi Vault keystores backend.
This allows to use Kubernetes based OIDC auth with
v3-operatorout of the box,without need to resort to additional tooling like
vault-agent.If OIDC parameters are passed instead of static token, the token will be acquired dynamically. Refresh will only happen if, during keystore secrets loading from Vault, previous token acquired via OID Connect is becoming expired and requests start to end up in 403. The fact of token being expired is deduced using
lease duration value received from Hashi Vault, when originally acquiring the token.