Ataccama ONE Agentic ONE Desktop ONE DQ&C ONE MDM ONE RDM ONE Runtime Server
latest (17.2.0) 17.1.0 17.0.0 16.3.x 16.2.0 16.1.0 16.0.0 15.4.0 15.3.0 15.2.0 15.1.0 14.5.x 13.9.x 13.8.x 13.7.x 13.6.x 13.5.0 13.4.x 13.3.x 13.2.x
Downloads

Unique Encryption Keys

Unique encryption keys secure the communication between ONE Desktop, its local runtime, and your Ataccama Cloud environment. Each environment gets its own encryption key, provided as a keystore file that you generate in the Ataccama Cloud Portal, which is the Ataccama Cloud administration and configuration interface. The same keystore is used by the self-managed Data Processing Engines (DPEs) connecting to the environment.

This page describes how to generate the keystore and configure ONE Desktop and the local runtime to use it. For configuring a self-managed DPE to use the keystore, see Unique Encryption Keys in the ONE documentation.

How unique encryption keys protect your environment

Using unique encryption keys contributes to the overall security of your deployment in the following ways:

  • Provides additional protection against unauthorized access to your data and environment in Ataccama Cloud.

  • Keeps data encrypted and compliant with data protection regulations.

  • Helps mitigate data leakage risks and protects data in transit and at the edge of the network.

  • Secures communication between Ataccama ONE and edge components, such as self-managed DPEs and ONE Desktop.

Unique encryption keys can be rotated and securely backed up and restored without getting embedded in the backup.

The keys are stored in a Java Cryptography Extension (JCE) keystore file (keystore.jceks). In the Helm values.yaml file generated by the Cloud Portal for Kubernetes-based DPE installations, the keystore is embedded as a Base64-encoded string.

Generate the keystore in the Cloud Portal

All edge components connecting to the same environment must use the same keystore.

If your environment is not managed through the Cloud Portal, contact Ataccama Support to obtain the keystore and its password.

To generate the keystore in the Cloud Portal:

  1. In the Cloud Portal, go to your environment and switch to the Services tab.

  2. In Shared Services, find ONE Desktop and select Instructions.

  3. In Use keystore file, select Generate.

  4. Once the keystore is ready, download the keystore file (Download keystore.jceks) and copy the corresponding password.

    Keep the dialog open until you finish configuring all components in case you need to return to it. Otherwise, you have to generate a new keystore and password.
    The ONE Desktop instructions dialog in the Cloud Portal with the Download keystore.jceks option and the keystore password

Configure ONE Desktop to use the keystore

  1. Navigate to your ONE Desktop installation folder.

  2. Open the one-desktop.ini file in a text editor.

  3. Add the following properties. Make sure to provide the correct path to the downloaded keystore as well as the keystore password (see Generate the keystore in the Cloud Portal, step 4).

    The key alias initial_peripheral applies to keystores generated in the Cloud Portal. If you obtained the keystore from Ataccama Support, use the alias provided with it.

    -Dproperties.encryption.keystore=[PATH_TO_DOWNLOADED_KEYSTORE_FILE]
-Dproperties.encryption.keystore.password=[KEYSTORE_FILE_PASSWORD]
-Dproperties.encryption.keyAlias=initial_peripheral
-Dinternal.encryption.keystore=[PATH_TO_DOWNLOADED_KEYSTORE_FILE]
-Dinternal.encryption.keystore.password=[KEYSTORE_FILE_PASSWORD]
-Dinternal.encryption.keyAlias=initial_peripheral

  4. Save your changes.

  5. To apply the properties to the local runtime, launch ONE Desktop.

  6. Go to Window > Preferences > Java > Installed JREs.

  7. Select the default JRE and then Edit.

  8. In Default VM arguments, paste the properties listed in step 3.

  9. Select Finish and then Apply and Close to save the changes.

    Editing default JRE

See also

Was this page useful?