Skip to content

feat(stack-kms-azure): Azure Key Vault and Managed HSM key vendor backend (CIP-5309) - #1531

Draft
freshtonic wants to merge 4 commits into
james/cip-5308-google-cloud-kms-key-vendor-backend-stack-kms-gcpfrom
james/cip-5309-azure-key-vault-key-vendor-backend-stack-kms-azure
Draft

freshtonic wants to merge 4 commits into
james/cip-5308-google-cloud-kms-key-vendor-backend-stack-kms-gcpfrom
james/cip-5309-azure-key-vault-key-vendor-backend-stack-kms-azure

Conversation

@freshtonic

@freshtonic freshtonic commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Layer 8 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).

@freshtonic
freshtonic added this pull request to stack #1523 November 6, 2026 00:47
@freshtonic freshtonic changed the title james/cip 5309 azure key vault key vendor backend stack kms azure feat(stack-kms-azure): Azure Key Vault and Managed HSM key vendor backend (CIP-5309) Nov 6, 2026
@changeset-bot

changeset-bot Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: d6e2eda

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

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

@github-actions

github-actions Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Mutation testing (cargo-mutants, --in-diff, stack-auth + stack-encrypt)

caught missed unviable timeout
60 0 94 0

Every mutant in the changed lines was caught by a test.

@freshtonic
freshtonic force-pushed the james/cip-5309-azure-key-vault-key-vendor-backend-stack-kms-azure branch 2 times, most recently from d375388 to c6c6614 Compare November 6, 2026 05:10
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
freshtonic force-pushed the james/cip-5309-azure-key-vault-key-vendor-backend-stack-kms-azure branch from c6c6614 to d6e2eda Compare November 6, 2026 05:13

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant