Secret key generator is a step in the Cryptography Plugin for Process Studio Workflows. The Secret Key Generator step is used to generate a random key (secret key) for algorithms such as DES, AEC, TripleDES, which can be used for symmetric encryption of data.

No. | Field Name | Description |

1 | Step name | Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow. |

Output fields: | ||

1 | Secret key field | Specify the name of the field that contains the generated secret key. |

2 | Algorithm field | Specify the name of the field that contains the the algorithm the generated secret key is used with. |

3 | Secret key length field | Specify the name of the field that contains the bit-length of the generated secret key. |

4 | Output key as binary | Enable this checkbox if you want the secret key to be returned in the native binary form. Otherwise, the secret key will be encoded in hexadecimal form. |

Secret key: | ||

1 | Algorithm | Specify the name of the Cipher algorithm that should be used to generate the secret key. |

2 | Scheme | Specify the name of the Cipher tranformation type that you would like to use. Leave empty for the default value used with the Algorithm. A default set of required Cipher Transformation types is available in Oracle Javadocs: https://docs.oracle.com/javase/7/docs/api/javax/crypto/Cipher.html |

3 | Key length | The bit-length of the secret key to be generated. For DES, the Key length can be 56. For DESede (Triple DES), the Key length can be 112 or 168. For AES, the Key length can be 128, 192, or 256. |

4 | How many? | The number of rows that should be generated with these Secret Key settings. |

Symmetric Cryptography is a step in the Cryptography Plugin for Process Studio Workflows. Symmetric Cryptography step is used to Encrypt or decrypt a string using symmetric encryption. Available algorithms are DES, AEC, TripleDES.

Note: Encrypting data with an AES key that has a key length of 192 or higher requires the Java Cryptography Extension, which allow unlimited strength cryptography. Without the JCE extensions, only AES with a key-length of 128 bits is supported. DES and DESede (Triple DES) are not affected.

No. | Field Name | Description |

1 | Step name | Name of the step as it appears in the workflow workspace. This name has to be unique in a single workflow. |

Crypto Settings: | ||

1 | Operation | Encrypt or Decrypt the message using the specified Secret key |

2 | Algorithm | The algorithm to be used to encrypt or decrypt the message |

3 | Scheme | The Cipher transformation type to be used with the Algorithm. This can be left empty for the default setting |

4 | Secret Key | The Secret Key to be used to encrypt or decrypt the message. |

5 | Secret key defined in a field | Enable to read the Secret Key from the incoming row, instead of from the Secret Key field |

6 | Secret Key field | If Secret key defined in a field above is enabled, provide the name of the field in the incoming stream that contains the Secret Key |

7 | Read key as binary | Enable Read key as binary if you want the secret key to be read in the native binary form from the incoming row. Otherwise, the secret key will be encoded in hexadecimal form. |

Message: | ||

1 | Message Field Name | Specify the name of the field in the incoming row that contains the message to be encrypted or decrypted |

Results Fields: | ||

1 | Result Fieldname | Specify the name of the field in the outgoing row that contains the result of the encryption or decryption operation |

2 | Save result as binary | Enable Save result as binary checkbox to store the result of the encryption or decryption operation as binary in the outgoing row. Otherwise, the result is stored as a string. |