The JWT Generation Data Operation allows for generating JSON Web Tokens using RSA or HMAC algorithms.

Use Cases

• Generate a JWT Token for some APIs to get access

Data Operation Properties

Payload (required)

Expects type Any.

Contains the claims to generate the JWT token. For more information, see https://jwt.io/introduction.

For all payloads, if iat is not present, then the iat (issued at) field is appended automatically.

Header (optional)

Expects type Any.

It consists of two parts: the type of the token, which is JWT, and the signing algorithm being used, such as HMAC or RSA.

In case no Header is provided, "alg" is populated according to the chosen algorithm, and "typ": "JWT" is added for object payloads automatically

The alg property in the Header is optional, as this is automatically chosen based on the algorithm selected from the drop-down menu. But if the "alg": ABC is present in the Header, then ABC must match the algorithm selected in the drop-down

RSA Private Key or HMAC Secret (required)

Expects type Text.

The secret (using HMAC) or public/private key pair (using RSA) to sign into the JWTs. This private key must be in PKCS1 or PKCS8 format.

Algorithm (required)

The algorithm to be use to generate the JWT: HS256, HS384, HS512, RS256, RS384, or RS512

Run Results

If successful, this data operation returns a JWT token.