You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Layer 7 of the CIP-5203 stack. Implements CIP-5309.
New crate stack-kms-azure: Key Vault REST 7.4 wrapkey/unwrapkey. RSA keys use RSA-OAEP-256; Managed HSM oct-HSM keys use A256KW. Both key modes.
Azure has no AAD, so the AAD is bound with stack_kms_vendor::bound. The wrapped key is padded to 72 bytes.
The stored form carries the versioned kid, so an unwrap needs no extra lookup.
Credentials: client secret, workload identity, managed identity (IMDS and App Service), and a static token. Client-certificate auth is deferred.
The shipped crate does not use rsa; it is only a dev-dependency, used by the emulator.
Opt-in live workflow integration-azure-key-vault.yml. It needs the variable STACK_KMS_AZURE_LIVE_KEY (optionally also STACK_KMS_AZURE_LIVE_HSM_KEY) and the secrets STACK_KMS_AZURE_TENANT_ID, STACK_KMS_AZURE_CLIENT_ID and STACK_KMS_AZURE_CLIENT_SECRET.
Decisions are in docs/plans/2026-11-05-key-vendor-backends-decisions.md (CIP-5309 section).
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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
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.
Layer 7 of the CIP-5203 stack. Implements CIP-5309.
stack-kms-azure: Key Vault REST 7.4wrapkey/unwrapkey. RSA keys use RSA-OAEP-256; Managed HSM oct-HSM keys use A256KW. Both key modes.stack_kms_vendor::bound. The wrapped key is padded to 72 bytes.kid, so an unwrap needs no extra lookup.rsa; it is only a dev-dependency, used by the emulator.integration-azure-key-vault.yml. It needs the variableSTACK_KMS_AZURE_LIVE_KEY(optionally alsoSTACK_KMS_AZURE_LIVE_HSM_KEY) and the secretsSTACK_KMS_AZURE_TENANT_ID,STACK_KMS_AZURE_CLIENT_IDandSTACK_KMS_AZURE_CLIENT_SECRET.Decisions are in
docs/plans/2026-11-05-key-vendor-backends-decisions.md(CIP-5309 section).