Skip to content

The Table: JWT Encode step signs the JSON in a payload column and writes the token to a new text column, one token per row. The output table is a copy of the source with that column added.

  • Source Table and Output Table — the table to read and the table to write.
  • Algorithm — HS256, HS384, HS512, RS256, RS384, or RS512.
  • Payload column — the column holding the JSON payload to sign.
  • Header column (optional) — a column holding a JSON header. It’s merged over the default header {"alg": …, "typ": "JWT"}.
  • Key column (optional) — a column holding the signing key. Without it, the step signs with the key held by its connection.
  • Output column — the name of the text column that receives the token.

A converted Savant analysis signs with a key held in a dedicated connection bound to the step, so the key never appears in the step configuration. See Migrate Savant Analyses.