Repository navigation
feat(azure-key-vault): add managed identity authentication to secret provider plugin - #189
Merged
michaelelrom merged 1 commit intoOct 29, 2026
Conversation
…provider plugin The plugin only supported a service principal with a client secret. When Itential Gateway runs on an Azure VM, it can now use the VM's managed identity instead, so there is no client secret to create, store, or rotate. Authentication is chosen from the provider configuration. If AZURE_CLIENT_SECRET_FILE or AZURE_CLIENT_SECRET is set, behavior is unchanged (client credentials grant). Otherwise the plugin requests a Key Vault token from the Azure Instance Metadata Service. AZURE_CLIENT_ID is optional in that mode and only selects a user-assigned identity. An empty AZURE_CLIENT_SECRET_FILE still fails instead of silently falling back to the managed identity. The README documents managed identity setup, registration and troubleshooting alongside the existing service principal steps. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or 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
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.
Add managed identity authentication to secret provider plugin
The plugin only supported a service principal with a client secret. When Itential Gateway runs on an Azure VM, it can now use the VM's managed identity instead, so there is no client secret to create, store, or rotate.
Authentication is chosen from the provider configuration. If AZURE_CLIENT_SECRET_FILE or AZURE_CLIENT_SECRET is set, behavior is unchanged (client credentials grant). Otherwise the plugin requests a Key Vault token from the Azure Instance Metadata Service. AZURE_CLIENT_ID is optional in that mode and only selects a user-assigned identity.
An empty AZURE_CLIENT_SECRET_FILE still fails instead of silently falling back to the managed identity.
The README documents managed identity setup, registration and troubleshooting alongside the existing service principal steps.