Add reference docs for the GCP Cloud KMS cryptography component - #5294
Open
FenjuFu wants to merge 1 commit into
Open
Add reference docs for the GCP Cloud KMS cryptography component#5294FenjuFu wants to merge 1 commit into
FenjuFu wants to merge 1 commit into
Conversation
Documents the new crypto.gcp.kms component: metadata properties, authentication, how keys and key versions are referenced, and the supported algorithms with the Cloud KMS key algorithms they map to. Signed-off-by: FenjuFu <92919259+FenjuFu@users.noreply.github.com>
4 tasks
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
1 participant
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
Adds the reference page for the new GCP Cloud KMS cryptography component (
crypto.gcp.kms), implemented in dapr/components-contrib#4538.The page covers the component YAML, the
project_id/location/keyRing/requestTimeoutmetadata, authentication with Application Default Credentials or explicit service account fields, the IAM permissions the identity needs, how keys and key versions are referenced, and a table mapping each supported Dapr algorithm to the Cloud KMS key algorithm behind it.It also documents the behaviors that follow from the Cloud KMS API surface: symmetric keys manage the nonce and tag internally, asymmetric encryption happens inside Dapr with the public key (Cloud KMS only exposes asymmetric decryption), OAEP labels are not supported, only symmetric keys can be wrapped, and signatures are verified locally because Cloud KMS has no verification API.
Issue reference
Documentation for dapr/components-contrib#3087.