-
Notifications
You must be signed in to change notification settings - Fork 49
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
Facilitate use of User Managed Identities #277
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (I can't think of any way to unit test this that would provide any real value), and I looked through the changes for both Azure dependency updates and nothing stood out.
The go.sum could use a cleanup through go mod tidy
Yeah, testing it in Azure was a pain too, even w/ terraform, but I did set up one user managed identity, tested it with and without client_id (and no client_secret), then two, one with permissions to access key vault and one without, so I could verify that the client_id was taking effect to select each one. |
* wip * tidy Original commit: 0ea6bba
* wip * tidy Original commit: 0ea6bba
* wrappers/transit: support context cancelation (hashicorp#259) This makes the transit client respect context cancelation, which is a critical feature of any I/O API. Original commit: 05c77e8 * Support parseutil.ParsePath for sensitive values in wrapper configs (hashicorp#272) and Use ParsePaths to source sensitive wrapper config values from Env/File if desired (hashicorp#275) * Add support for stdlib ParsePath to sensitive options * wip * wire up QuietParsePath to all remaining wrappers * Add ParsePaths * wip new pattern * bug fixes * remove unused * unit test * mod tidy * remove unnecessary change * remove unnecessary change * Use the new parsepath options * add missing errnoturl check * Update to parsepath 0.1.9 * rollback wrapper changes until we have a tagged top level package * Improve ParsePaths behavior in errors, and add a usage comment Original commit: a1337fd --- * Add support for stdlib ParsePath to sensitive options * wip * wire up QuietParsePath to all remaining wrappers * Add ParsePaths * wip new pattern * bug fixes * remove unused * unit test * mod tidy * remove unnecessary change * remove unnecessary change * Use the new parsepath options * add missing errnoturl check * Update to parsepath 0.1.9 * update go.mods to point to a fixed tag for ParsePath * go mod tidy * pr feedback Original commit: 9aac87b * Facilitate use of User Managed Identities (hashicorp#277) * wip * tidy Original commit: 0ea6bba * Fix the fact that some GCP env vars are immune to disallowEnvVars (hashicorp#250) Original commit: 24f9019 * Fix transit context cancellation test Signed-off-by: Alexander Scheel <[email protected]> * Add wrapping.ParsePaths(...) to pkcs11 Signed-off-by: Alexander Scheel <[email protected]> * Bump openbao/api & openbao/sdk to latest versions Signed-off-by: Alexander Scheel <[email protected]> --------- Signed-off-by: Alexander Scheel <[email protected]> Co-authored-by: Johan Brandhorst-Satzkorn <[email protected]> Co-authored-by: Scott Miller <[email protected]>
User managed identities in Azure are referenced only by client_id (if at
all), and don't use a client_secret. When client_secret is absent in wrapper
config, attempt to use this form of credential.
Fixes https://hashicorp.atlassian.net/browse/VAULT-32283 and https://hashicorp.atlassian.net/browse/VAULT-33015