Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Expandpanel
titleContents

Table of Contents
indent15px
stylenone

...

Destination Encryption allows storage of sensitive data from different publishers in a secured way. Encryption implies the transformation of plain text into cipher text or vice-versa by using key

Destination Encryption Characteristics

In Destination Encryption, all messages sent to a particular destination (topic or queue) are encrypted, thus providing a secure channel of delivery. A component does not have to encrypt the message explicitly like in Message Encryption. A destination is marked as encrypted at the time of its creation. All messages published on this destination are encrypted before storing those in the database and delivered decrypted to subscribing applications. A client application, therefore, does not have to explicitly decrypt a received message.

Base Implementation

Fiorano versions above 9.5.0 support Destination Encryption. DES (Data Encryption Standards) is used as the default encryption algorithm. In addition to that, Fiorano supports Base64, TripleDES, AES256, AES128, AES192, RC2-40, RC2-64, and RC2-128 standards too.

...

Destination Encryption involves only encrypting the payload of the message and not its JMS headers and properties.

Encrypted Destination Creation

Input/Output port properties appear in the Properties pane when an input port of a component instance is selected. Encryption properties can be configured in the input/output ports from the JMS Destination tab under the Properties panel.

...

Encrypt/Decrypt feature is used for security purpose to encrypt the data in output response generated from components so that the sensitive data will be more secure from normal users. Encrypted data in a flow can be decrypted after receiving the encrypted data at the component's input port as per the details in the Encrypt/Decrypt configuration page. The steps involved in enabling the encrypt/decrypt feature has been described as below:

Adding KeyStore Configuration

  1. In eStudio, open Configuration Repository panel (Window > Show View > Other > Fiorano), right-click on Resource and select Add Configuration option to open the dialog box for adding new Resource Configuration.


    Figure 2: Navigating to add keystore configuration

  2. Select the Resource Type as "Keystore" and click Next.


    Figure 3: Choosing Keystore Resource Type in Resource Configuration Window

  3. Click on Next and provide any String of your choice (recommended minimum of 6 characters for better security) and click Finish to save the keystore which will be used as the key for encryption/decryption of data.


    Figure 4: Adding Encryption Key

...

Adaptavist ThemeBuilder EngineAtlassian Confluence