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

Add support for Vault Agent's Auto-Auth feature #162

Open
jmcconnell opened this issue Aug 24, 2023 · 0 comments
Open

Add support for Vault Agent's Auto-Auth feature #162

jmcconnell opened this issue Aug 24, 2023 · 0 comments

Comments

@jmcconnell
Copy link

jmcconnell commented Aug 24, 2023

Vault Agent provides an Auto-Auth capability where the agent is responsible for managing and using the token but a proxy API is provided so that clients no longer need to submit an X-Vault-Token header with requests. quarkus-vault is currently configured to omit this header if the configured token is null, but I don't see a safe way of eliciting this behavior (please correct me if I've overlooked something.)

Would it be possible to update the VaultRuntimeConfig#authentication() signature to return an Optional<VaultAuthenticationConfig> and add a new configuration property that allows this to be None? My company's internal cloud service has stopped passing wrapped client tokens to cloud services in favor of an Auto-Auth-enabled Vault Agent sidecar, so I don't currently see another authentication option that will work with quarkus-vault, as-is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant