Azure Native Authentication Method #1833
Merged
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.
Description 📣
This PR adds the new Azure authentication method to Identities.
With this method, Azure resources like Azure VMs avoid secret zero by not needing to store an additional token to authenticate with Infisical. Instead, they can use their managed identity access tokens to prove their identity to Infisical — this works by relaying the managed identity access token through Infisical to be verified against the public key at the Azure AD OpenID configuration endpoint; if successful and certain allow conditions are met, then the entity is considered authenticated and an access token granting access to the Infisical API is returned.
Workflow:
/api/v1/auth/azure-auth/login
endpoint containing theidentityId
that they are authenticating as and thejwt
as params (in practice this would likely be done via SDK or other client but it can also be done manually).oid
field on the JWT payload) against Allowed Service Principal IDs defined in step 1.Note: The Azure authentication method will require additional engineering work for clients like Infisical Agent and SDKs to support it.
Type ✨