Twofish Encrypt



Snap type:

Transform



Description:

This Snap encrypts the binary documents that it receives on its input view using the Twofish algorithm and user-specified encryption parameters.

The default security in the JRE limits the key length for encryption keys. For stronger encryption keys, you would need to manually install the Java Cryptographic Extension JARs on your JCC nodes.

  • Expected Upstream Snaps: Any Snap that produces binary data in the output view such as File Reader or Compress.

  • Expected Downstream Snaps: Any Snap that accepts binary data in the input view such as File Writer or Decompress.

  • Expected input: Stream of binary decrypted data with the encryption details required to encrypt the streaming data.

  • Expected output: Stream of binary encrypted data.



Prerequisites:

[None]



Support and limitations:

Works in Ultra Task Pipelines.

Account: 

This Snap uses account references created on the Accounts page of the SnapLogic Manager to handle access to this endpoint. This Snap supports a Symmetric crypto account, or no account. See Configuring Binary Accounts for information on setting up accounts that work with this Snap.



Views:





Settings

Label



Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.

Password





The string that is used to generate a secret key and an initialization vector. If the secret key property is set, the password is ignored.
Example: K1qjoeFQTr

This field is currently not encrypted at rest and is saved and exported in plaintext. For any shareable secrets that require encryption at rest, we recommend you use a Secret key in the Symmetric Crypto Account. Using a Symmetric Crypto Account ensures that your sensitive information is protected and secure. 

Secret key



The secret key that is used for encryption.

Example: VsWLDQMvz9LaCaB3aaDHBw==

This field is currently not encrypted at rest and is saved and exported in plaintext. For any shareable secrets that require encryption at rest, we recommend you use a Secret key in the Symmetric Crypto Account. Using a Symmetric Crypto Account ensures that your sensitive information is protected and secure. 

Initialization vector



The initialization vector that is used for encryption. It should be in hexadecimal format and should not be used in ECB mode.
Example: 6df68cdf3a6c48b2fde727541f3cecc



Cipher mode

Required. The mode of operation for a block cipher.

The available options include: ECB, CBC, CFB, CFB8, CFB16, CFB24, CFB32, CFB40, CFB48, CFB56, CFB64, OFB, OFB8, OFB16, OFB24, OFB32, OFB40, OFB48, OFB56, OFB64, SIC.

Default value:  ECB



Encryption padding

Required. The encryption padding. 

The available options include: TBCPADDING, PKCS5PADDING, ISO10126PADDING, NOPADDING.

Default value:  TBCPADDING



Snap Execution

Select one of the following three modes in which the Snap executes:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.

  • Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.

  • Disabled: Disables the Snap and all Snaps that are downstream from it.

Default Value: Execute only
Example: Validate & Execute