Key Capabilities
- Native AES encryption and decryption of message content, with no external tools or scripts required
- Multiple key sources (password-based key derivation, static key, or header-supplied key) and seven cipher modes
- Configurable nonce/IV handling, GCM authentication, password salt, and padding, with interoperability for content encrypted by OpenSSL
Overview
The AES connector performs native AES encryption and decryption of message content, replacing prior workarounds that required invoking OpenSSL through ArcScript and managing external processes. The connector offers two operations: Encrypt (the default) and Decrypt. You configure how keys, cipher modes, and metadata (such as nonces or IVs and authentication tags) are handled.The connector can decrypt content originally encrypted with OpenSSL (AES-CBC), provided the same key, IV, and padding configuration are used.
Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
The available settings depend on the selected Operation, Key source, and Cipher Mode.Configuration
Settings related to the core operation of the connector.| Setting | Description |
|---|---|
| Connector Id | The static, unique identifier for the connector. |
| Connector Type | Displays the connector name and a description of what it does. |
| Connector Description | An optional field to provide a free-form description of the connector and its role in the flow. |
Key
Settings related to the AES key. The available fields depend on the selected Key source. The following table shows the settings for Password-Based Key Derivation.Non-Default Key Options
- If you are using a Static Key, provide the Key as hexadecimal (prefixed with
0x) or Base64. The decoded key must be 16, 24, or 32 bytes (AES-128, AES-192, or AES-256). - If you are using a Header-supplied Key, binary values you enter accept hex (
0x) or Base64; binary values the connector generates and writes to headers are Base64-encoded. The decoded key must be 16, 24, or 32 bytes (AES-128, AES-192, or AES-256).
Non-Default Password Salt Options
- If you choose Static in Password Salt, use the Password Salt field to provide a value that decodes to exactly 16 bytes, as
0x-prefixed hexadecimal or Base64. - If you choose Header in Password Salt, enter the name of the message header used to read or write the password salt in the Password Salt Header field.
Cipher
Settings related to the cipher mode and nonce/IV handling.In Decrypt mode, the Nonce / IV Auto-Generate field changes to Included.
Authentication
GCM cipher mode only.Advanced Tab
Advanced Settings
Settings not included in the previous categories.Message
Message settings determine how the connector searches for messages and manages them after processing.
Note: The settings below are deprecated and hidden by default. They appear only on connectors where they were previously enabled or configured to a non-default value. To retain copies of successfully processed files, right-click the connector in the flow, choose Show Success Path, and connect the success path to a File connector.
| Setting | Description |
|---|---|
| Save to Sent Folder (Deprecated) | Copies files processed by the connector to the Sent folder. Disabled by default. Files saved to the Sent folder are not covered by Encryption at Rest. |
| Sent Folder Scheme (Deprecated) | Groups files in the Sent folder by the selected time interval. Only relevant when Save to Sent Folder is enabled. |
Logging
Settings that govern the creation and storage of logs.
| Setting | Description |
|---|---|
| Log Level | The verbosity of logs generated by the connector. When you request support, set this to Debug. |
| Log Subfolder Scheme | Instructs the connector to group files in the Logs folder according to the selected interval. The Weekly option (which is the default) instructs the connector to create a new subfolder each week and store all logs for the week in that folder. Leaving this setting blank tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance. |
| Log Messages | Check this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the Transactions tab. |
Miscellaneous
Miscellaneous settings are for specific use cases.
| Setting | Description |
|---|---|
| Other Settings | Enables you to configure hidden connector settings in a semicolon-separated list (for example, setting1=value1;setting2=value2). Normal connector use cases and functionality should not require the use of these settings. |
Automation Tab
Settings
Settings related to the automatic processing of files by the connector.Performance
Settings related to the allocation of resources to the connector.
| Setting | Description |
|---|---|
| Max Workers | The maximum number of worker threads consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page. |
| Max Files | The maximum number of files sent by each thread assigned to the connector. If set, this overrides the default setting on the Performance Settings portion of the Advanced Settings page. |