Sign

cloud_kms.sign
ActionGoogle Cloudconnection required

Calls Cloud KMS POST cryptoKeyVersions/{v}:asymmetricSign.

Sign the SHA-256 digest of text with an asymmetric KMS key version.

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

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

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
KMS location (overrides connection).
stringNo———
key_ring
Key ring id (overrides connection).
stringNo———
key
CryptoKey id.
stringYes———
key_version
Key version id.
stringNo1——
text
Text to sign (SHA-256 digest is computed).
stringYes———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "key_version": "1"
}

Input

Fallback source of the text.

FieldTypeExample
text
Text to sign; read when the config leaves text blank.
string—

Output

One shape.

result

FieldTypeExample
ok
boolean—
signature
string—
key_version
string—
digest_sha256
string—
{
  "digest_sha256": "",
  "key_version": "",
  "ok": false,
  "signature": ""
}

See Sign 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.