Decapsulate Crypto Key Version

cloud_kms.decapsulate_crypto_key_version
ActionGoogle Cloudconnection required

Calls cloudkms v1 POST /v1/projects/{projectsId}/locations/{locationsId}/keyRings/{keyRingsId}/cryptoKeys/{cryptoKeysId}/cryptoKeyVersions/{cryptoKeyVersionsId}:decapsulate.

Decapsulates data that was encapsulated with a public key retrieved from GetPublicKey corresponding to a CryptoKeyVersion with CryptoKey.purpose KEY_ENCAPSULATION.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud KMS
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id, location, key_ring
Resolved by
config.connection_id, else node.connection_id

Configuration

5 fields, 4 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
location
Location or region; taken from the connection when unset.
stringNo———
key_ring
Key ring name or id.
stringYes———
crypto_key
Crypto key name or id.
stringYes———
crypto_key_version
Crypto key version name or id.
stringYes———
body
The DecapsulateRequest resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
name
string—
protectionLevel
string—
sharedSecret
string—
sharedSecretCrc32c
string—
verifiedCiphertextCrc32c
boolean—
{
  "name": "",
  "protectionLevel": "",
  "sharedSecret": "",
  "sharedSecretCrc32c": "",
  "verifiedCiphertextCrc32c": false
}

See Decapsulate Crypto Key Version run in a workflow.

In a technical demo we add the Google Cloud KMS connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.