The Encryption component is used for encrypting data, based on a key (that is entered by the user) and an algorithm.

This component also can handle digest data. If the message is signed/digested by the sender, the recipient can verify if the message is from the correct sender and if the message didn't change during transmission.

The supported algorithms are DES, PGP, PGP_RFC4880, Base64, TripleDES, AES256, AES128, RC2-40, RC2-64, and RC2-128.

Configuration and Testing

Interaction Configuration

The component has the following attributes which can be configured from its Configuration Property sheet. Figure 1 illustrates the panel with Expert Properties enabled.

Figure 1: Configurable properties for Encryption component

Encryption Configuration

Encryption Details consists Data Encryption Information and Signing Information.

Data Encryption Details

Figure 2: Encryption Algorithm Details

Encryption Algorithm Name

Select the algorithm to be used for encryption. The supported algorithms are DES, PGP, PGP_RFC4880, Base64, TripleDES, AES256, AES128, RC2-40, RC2-64, and RC2-128.

The following are the configurations of the individual algorithms.

DES Encryption Algorithm Configuration

For DES, the configuration panel is as shown in the Figure 2. Set the following fields accordingly.

  • Encryption Key: Specify key which is used to encrypt the incoming data. Specify 32 digit key for AES256, 16 digit key for AES128, 16 digit key for DES, 24 digit key for TripleDES, 5 digit key for RC2_40, 8 digit key for RC2_64 and 16 digit key for RC2_128
  • Allow Padding: Enable this property to allow padding to the key to make exactly the value required for the mentioned algorithm. It has to be chosen only when we know that encrypted data key is also padded.
AES256, AES192, AES128, TripleDES Encryption Algorithm

Figure 3: AES256, AE192, AE128, TripleDES algorithm encryption

  • Set the Encryption key and the Padding key details similar to the DES algorithm.
  • Initialization Vector : Mention the unique 64 bit input used in the encryption.
RC2_40, RC2_64,RC2_128 Encription Algorithm Configurations

Figure 4: RC2_40, RC2_64,RC2_128 Algorithm Encription

  • Provide the encryption in the same way as for the DES algorithm .
PGP Encryption Configuration

Figure 5: PGP, PGP_RFC4880 Algorithm Encryption

  • Sign : Select this option to sign the message when the algorithm used is PGP.
  • Public Key File: Specify public key file used in case of PGP Algorithm
  • Private Key File: Specify private key file used in case of PGP Algorithm
  • Passphrase: Required for signing in case of PGP algorithm.
RSA Encryption Configuration

Figure 6: RSA algorithm encryption

Key Source:There are four options under Key Source :

  1. Text: This requires the Encription Key details
    • Encryption Key : Specify the appropriate Encryption Key for the selected algorithm to be used to decrypt the incoming data..
  2. PublicKeyFile: The public Key File field has to be filled for this.
    • Public Key File: Provide the file containing the public key.
  3. Private Key File :The Private Key Password and the Private Key File are the active fields under this.
    • Private Key password: Provide the private key password.
    • Private Key File: Provide the file containing the Private Key
  4. Certificate: Certificate File is the active field when the key source is Certificate.
    • Certificate File: provide the path of the X509 Certificate.

Digest Encryption Details 

Figure 7: Digest type used for verifying digested data can be provided as given above.

  • SignData: Select to verify only when you know that encrypted data has been signed.
  • DigestType: The supported algorithms for signing/digesting data are are MD5, SHA-1, SHA-256, SHA-384 and SHA-512.
Encryption Algorithm Name

Specify the encryption details which are used to encrypt the signed data. It is done in the same way as shown in Data Encryption Details. Algorithm for data encryption and digest data encryption need not be same.

The following Encryption Algorithms are available:

  • DES
  • AES256
  • AES128
  • AES192
  • RC2_40
  • RC2_64
  • RC2_128
  • TripleDES
  • PGP
  • Base64Encoding
  • RSA

The individual configurations are similar to that of Data Encryption Details.

Binary Output Required

Enable this property if Binary Output is needed. Else encrypted data will be in XML format.

Encode Data

Encode Data after encrypting using Base64 encoding scheme, This option will help in avoiding characters of encrypted data included in the output XML generated if Binary Output option is not selected.

Only Sign Data

Check this option if the data has to be only signed without Encrypting.
Input to Encryption component can be in xml format. XML format is shown in Figure 4. The values of Encryption Algorithm Parameters and Digest Parameters can be mentioned or else these values are taken from cps.

Read Input From File?

Choose this option to read input from a file instead of component input port.

Input File Directory

Directory where the input file is located.

Input File Name

Name of the input File.

Write output to File?

Select this option if output is to be written into a file.

Output File Directory

Directory where output file needs to be stored.

Output File Name

Name of the output file.

Sample input

Figure 8: Sample Input

Sample output

Figure 9: Output for the Sample Input

Functional Demonstration

Scenario 1

Encryption of data received from input.

Configure the Encryption component as described in Configuration and Testing section  and use feeder and display component to send sample input and check the response respectively.

Figure 10: Event Process flow for Scenario 1

Sample Input

Figure 6: Sample Input

Sample Output

Figure 11: Sample Output in binary format

Figure 12: Sample Output in xml format

Use Case Scenario

In a bond trading scenario, request for quotes (RFQ) are sent in encrypted form to the appropriate exchanges and the received encrypted responses are decrypted at the user end.

Figure 13: Event Process for Bond Trading Scenario

The event process that demonstrates this scenario is bundled with the installer. Note encryption and decryption components may not be present.

Documentation of the scenario and instructions to run the flow can be found in the Help tab of the flow present in eStudio.


Adaptavist ThemeBuilder EngineAtlassian Confluence