Important AES Encryption Update

Process Director is implementing a newer, modern encryption system in the product, which will replace the encryption that was originally used. This encryption change provides higher security, but it does affect the migration process the first time--and ONLY the first time--you install v5.44.700 or higher from v5.44.600 or lower (except for load-balanced installations). Upgrading from v5.44.700 to any higher version will require no special action for most customers.

Please refer to the Upgrading to a Newer Version section of the Reinstall/Upgrades/Moving Hosts topic of the Installation guide, which covers the upgrade process for most customers.

Customers who manage a load-balanced installation are subject to some additional considerations, which are documented in the Installation Settings section of the Load Balancing, Standby, and Rendering Options topic of the System Administration Guide.

On-premise customers who decide NOT to upgrade to v5.44.700, should also make a specific change to their installation. BP Logix recommends that you manually edit your installation's web.config file to direct Internet Information Server to provide an auto-generated cryptographic key that will be unique to your installation.

To do so, you should edit the machineKey configuration setting in the system.web section of the web.config file so that it looks like the example highlighted in red below.

<configuration>
    // Some other configuration settings may appear here
    <system.web>
        <machineKey
            validationKey="AutoGenerate,IsolateApps" validation="HMACSHA512"
            decryptionKey="AutoGenerate,IsolateApps" decryption="AES" />
        // Some other configuration settings may appear here
    </system.web>
    // Some other configuration settings may appear here
</configuration>

Once you've made this change and saved the web.config file, the system will recompile and new AES encryption keys will be automatically generated for your installation.