With the Encryption connector, you can use commands in a chain to encrypt or decrypt files or plaintext using Pretty Good Privacy (PGP) keys or X.509 certificates.
Note: For PGP encryption, the connector supports Advanced Encryption Standard (AES)-128; for PGP decryption, AES-128, AES-256, CAST-128 (CAST5), and Triple Data Encryption Standard (3DES).
To set up the connector, you'll need:
- The PGP or X.509 public key file to use for encryption
- The public key's corresponding private key file for decryption
- The private key's password (if applicable)
Set Up the Encryption Connector
- From Chains, click Connections and Add Connection .
- Under BizApp Connection, select Encryption and the default CloudRunner.
- Under Basic Info, enter a unique name and description to help identify the connection.
- Under Resources, upload the public key and private key files.
- Under Properties, enter the connection's details:
Property Details PGP Public Key File To encrypt with a PGP key, enter the filename of the public key file uploaded under Resources. PGP Private Key File To decrypt PGP encryption, enter the filename of the private key file uploaded under Resources. PGP Private Key Password Enter the password created with the PGP private key file, if applicable. If no password was created, leave blank. X509 Public Key File To encrypt with an X.509 certificate, enter the filename of the public key file uploaded under Resources. X509 Private Key File To decrypt X.509 encryption, enter the filename of the private key uploaded under Resources. X509 Private Key Password Enter the password created with the X.509 private key file, if applicable. If no password was created, leave blank.
Note: All sensitive credentials are automatically encrypted and stored at AES-256 encryption.
- Select the environments to use the connection, and click Save.
- To test the connection, create and run a chain with the connector's Encrypt with PGP Key or Encrypt with X509 Certificate command, and verify it returns a valid output.
If encryption or decryption fails:
- Verify the public and private key files entered under Properties match the files uploaded under Resources.
- Check the password entered for the private key file, if applicable.