ÃÛ¶¹ÊÓƵ

JWT module

The ÃÛ¶¹ÊÓƵ Workfront Fusion JWT app provides a module that creates JWT tokens based on the provided algorithm.

Access requirements

You must have the following access to use the functionality in this article:

ÃÛ¶¹ÊÓƵ Workfront plan*
Pro or higher
ÃÛ¶¹ÊÓƵ Workfront license*
Plan, Work
ÃÛ¶¹ÊÓƵ Workfront Fusion license**

Current license requirement: No Workfront Fusion license requirement.

Or

Legacy license requirement: Workfront Fusion for Work Automation and Integration, Workfront Fusion for Work Automation

Product

Current product requirement: If you have the Select or Prime ÃÛ¶¹ÊÓƵ Workfront plan, your organization must purchase ÃÛ¶¹ÊÓƵ Workfront Fusion as well as ÃÛ¶¹ÊÓƵ Workfront to use functionality described in this article. Workfront Fusion is included in the Ultimate Workfront plan.

Or

Legacy product requirement: Your organization must purchase ÃÛ¶¹ÊÓƵ Workfront Fusion as well as ÃÛ¶¹ÊÓƵ Workfront to use functionality described in this article.

To find out what plan, license type, or access you have, contact your Workfront administrator.

For information on ÃÛ¶¹ÊÓƵ Workfront Fusion licenses, see ÃÛ¶¹ÊÓƵ Workfront Fusion licenses.

JWT API information

The JWT connector uses the following:

API tag
v1.1.5

JWT module and its fields

Generate JWT

This module generates a JWT based on the selected algorithm.

Algorithm

Select algorithm with which you want to generate the JWT.

  • HS256: HMAC using SHA-256 hash algorithm
  • HS384: HMAC using SHA-384 hash algorithm
  • HS512: HMAC using SHA-512 hash algorithm
  • RS256: RSASSA-PKCS1-v1_5 using SHA-256 hash algorithm
  • RS384: RSASSA-PKCS1-v1_5 using SHA-384 hash algorithm
  • RS512: RSASSA-PKCS1-v1_5 using SHA-512 hash algorithm
  • PS256: RSASSA-PSS using SHA-256 hash algorithm (only Node ^6.12.0 OR >=8.0.0)
  • PS384: RSASSA-PSS using SHA-384 hash algorithm (only Node ^6.12.0 OR >=8.0.0)
  • PS512: RSASSA-PSS using SHA-512 hash algorithm (only Node ^6.12.0 OR >=8.0.0)
  • ES256: ECDSA using P-256 curve and SHA-256 hash algorithm
  • ES384: ECDSA using P-384 curve and SHA-384 hash algorithm
  • ES512: ECDSA using P-521 curve and SHA-512 hash algorithm
Payload
For each payload item you want to add, click Add item and enter the item's key and value.
Options

For each option item you want to add, click Add item and enter the item's key and value.

The following keys are available:

  • algorithm: (default: RS256)
  • expiresIn: Expressed in seconds or a string describing a time span (e.g., 2 days, 10h, 7d). A numeric value is interpreted as a seconds count. If you use a string, be sure to provide the time units (days, hours, etc.), otherwise milliseconds unit is used by default (120 is equal to 120ms).
  • notBefore: Expressed in seconds or a string describing a time span (e.g., 2 days, 10h, 7d). A numeric value is interpreted as a seconds count. If you use a string, be sure to provide the time units (days, hours, etc.), otherwise milliseconds unit is used by default (120 is equal to 120ms).
  • audience
  • issuer
  • jwtid
  • subject
  • noTimestamp
  • header
  • keyid
  • mutatePayload: If true, the sign function will modify the payload object directly. This is useful if you need a raw reference to the payload after claims have been applied to it but before it has been encoded into a token.
  • allowInsecureKeySizes: If true, allows private keys with a modulus below 2048 to be used for RSA.
  • allowInvalidAsymmetricKeyTypes: If true, allows asymmetric keys which do not match the specified algorithm. This option is intended only for backward compatibility and should be avoided.
recommendation-more-help
5f00cc6b-2202-40d6-bcd0-3ee0c2316b43