Repository navigation
feat(stack-kms-azure): Azure Key Vault and Managed HSM key vendor backend (CIP-5309) - #1531
Draft
freshtonic wants to merge 4 commits into
Conversation
|
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true |
Contributor
Mutation testing (cargo-mutants,
|
| caught | missed | unviable | timeout |
|---|---|---|---|
| 60 | 0 | 94 | 0 |
Every mutant in the changed lines was caught by a test.
freshtonic
force-pushed
the
james/cip-5309-azure-key-vault-key-vendor-backend-stack-kms-azure
branch
2 times, most recently
from
November 6, 2026 05:10
d375388 to
c6c6614
Compare
The backend supports Azure Key Vault and Managed HSM. It binds the associated data, versions the wrapped keys and supports Entra ID credentials.
Add hand-written Key Vault fixtures, a test-only RSA key and a live test. Run the contract suite over a Key Vault emulator for RSA and oct-HSM keys.
Check the WASI build. Stage the crate for crates.io.
freshtonic
force-pushed
the
james/cip-5309-azure-key-vault-key-vendor-backend-stack-kms-azure
branch
from
November 6, 2026 05:13
c6c6614 to
d6e2eda
Compare
This branch has not been deployed
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.
Layer 8 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).