Versions Compared

Old Version 49

changes.mady.by.user Eleanor Tesoro

Saved on

compared with

New Version 50

changes.mady.by.user Ruth Stento

Saved on

Key

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

In this article

...

Note
titleBest Practice
  • You cannot use a Cloudplex for this configuration. Before enabling this feature, you need to work with SnapLogic support to turn off and remove Cloudplex instances from your Org or convert them into Groundplex instances. You can, however, use Enhanced Encryption in an eXtremeplex. 
  • We do not recommend moving an Org from Enhanced Encryption to Standard Encryption. However, if the Org with Enhanced Encryption is moved to Standard Encryption, any OAuth 2.0 accounts created before do not function and therefore need to be re-created after the move.

...

  • Once Enhanced Account Encryption is enabled, you are not be able to see or edit the existing values for the encrypted data types.

...

  1. Install the latest Groundplex RPM/DEB on one of the Groundplex nodes which that is already running with enhanced encryption. This step is required to get the new addDataKey option in the jcc.sh script.

  2. As root user, run the following command:

    Code Block
    /opt/snaplogic/bin/jcc.sh addDataKey keyFeb2020


    This command generate generates a new key pair and append it to the keystore in /etc/snaplogic folder with the specified alias (keyFeb2020).

  3. You must copy the generated data keys files (jcc-datakeys.jks and jcc-datakeys.pass) from this node to all the others in the Org, similar to when originally setting up the enhanced encryption feature.

  4. Restart the nodes in the Org. This step is required to pick up the updated key pair. Each node can be restarted one at a time from the dashboard in order to do an online restart.

  5. Once all the nodes are running with the new key pair loaded, the Enhanced Encryption settings display the drop-down list allowing the Org admin to change to the new key.

...