Skip to Content

PGP (Beta) connector for Jitterbit Integration Studio

Summary

The PGP (Beta) connector allows for the encryption and decryption of files in compliance with the OpenPGP encryption standard.

The PGP (Beta) connector provides an interface for creating a PGP (Beta) connection, the foundation used for generating instances of PGP (Beta) activities.

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

Note

For beta access and to provide feedback, contact the Jitterbit Product Team.

Connector overview

This connector is used to first configure a PGP (Beta) 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 PGP (Beta) connection and its activities are referred to as a PGP (Beta) endpoint:

PGP activity types

  • Encrypt: Encrypts files and is intended to be used as a target in an operation.

  • Decrypt: Decrypts files 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 PGP (Beta) 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 PGP (Beta) connector uses the Bouncy Castle API v1.80 which implements the OpenPGP encryption standard. Refer to the API documentation for information on the schema nodes and fields. For more information on the OpenPGP specification, refer to IETF RFC 9580: OpenPGP.

Troubleshooting

If you experience issues with the PGP (Beta) connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

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

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

  4. If using private agents, you can enable connector verbose logging for this connector by adding this logger configuration entry to your private agent's logback.xml file:

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

    For more information on connector verbose logging, see Verbose logging for connectors using Jitterbit private agents.

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