Skip to Content

JWT connector for Jitterbit Integration Studio

Summary

The JWT connector allows for the generation, decoding, and validation of JSON Web Tokens (JWT). It does not connect to an external service for this functionality.

The JWT connector provides an interface for creating a JWT connection, the foundation used for generating instances of JWT activities.

The JWT connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Connector overview

This connector is used to first configure a JWT connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific JWT connection and its activities are referred to as a JWT endpoint:

JWT activity types

  • Generate Token: Generates a JWT and is intended to be used as a target in an operation.

  • Decode Token: Decodes a JWT and is intended to be used as a target in an operation.

  • Validate Token: Validates a JWT and is intended to be used as a target in an operation.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Prerequisites and supported API versions

The JWT connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

The JWT connector uses the Java JWT library. Refer to the API documentation for information on the schema nodes and fields. For more information on the JWT specification, refer to IETF RFC 7519: JSON Web Token (JWT).

Troubleshooting

If you experience issues with the JWT connector, these troubleshooting steps are recommended:

  1. Check the operation logs for any information written during execution of the operation.

  2. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  3. If using private agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:

    <logger name="org.jitterbit.connector.jwt" level="DEBUG"/>

  4. If using private agents, you can check the agent logs for more information.

  5. For additional troubleshooting considerations, see Operation troubleshooting.