-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Support AppRole for Vault Integration - Goal: Grouped Policies #2171
Comments
I would guess this issue also depends on hashicorp/consul-template#744 |
@c4milo Nomad's Vault integration is actually separate from consul-templates. We just hand CT a token but Nomad does all the heavy lifting of getting it. |
@justenwalker Talked to the Vault team a bit and they have some future work that should make default policies possible without AppRole. AppRole is another authentication backend which is less than ideal since Nomad already uses the token backend. I am going to keep this open but slightly rename the title. |
I'm reviewing open Vault issues following the new Vault workload identity work (ref #15617). We've implemented something roughly similar to what's been proposed here, using signed workload identities to login to Vault and then use roles defined for the auth config. Going to close this issue to tidy up. |
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. |
Currently, Nomad 0.5.x supports Vault via injecting a specific token with a list of policies in the job file. It would be good to use AppRoles to group these common policies together under a specific name.
Essentially, this would mean supporting something like:
And having the Nomad Client authenticate the task using the app role.
Caveat:
The text was updated successfully, but these errors were encountered: