Skip to content

Conversation

@oblakeerickson
Copy link
Contributor

@oblakeerickson oblakeerickson commented Dec 16, 2025

Now that we have migrated to v-api in db07e89 we need to update the config.example.toml file to match our new reality.

This commit updates the Local key section and the Cloud KSM section to specify a signer and a verifier.

Addresses part of #368

Now that we have migrated to v-api in db07e89 we need to update the
config.example.toml file to match our new reality.

This commit updates the Local key section to specify a signer and a
verifier and removes the deprecated ckms key type.

Address part of oxidecomputer#368
@augustuswm
Copy link
Contributor

Thanks for updating this in the docs. We do still support CKMS as a key backend in addition to local keys. For the CKMS option it would look like this:

# Cloud KMS
[[keys]]
kind = "ckms_signer" # Static identifier indicating Cloud KMS
kid = "" # Unique key identifer, that will be used in JWKS
version = 1 # KMS key version
key = "" # KMS key name
keyring = "" # KMS keying name
location = "" # KMS region
project = "" # GCP project containing Cloud KMS

[[keys]]
kind = "ckms_verifier" # Static identifier indicating Cloud KMS
kid = "" # Unique key identifer, that will be used in JWKS
version = 1 # KMS key version
key = "" # KMS key name
keyring = "" # KMS keying name
location = "" # KMS region
project = "" # GCP project containing Cloud KMS

@oblakeerickson
Copy link
Contributor Author

Ah I see. Makes sense you wouldn't just get rid of cloud kms support. Updated my original PR comment too.

@augustuswm augustuswm merged commit d2f7513 into oxidecomputer:main Dec 16, 2025
4 checks passed
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.

2 participants