Replacing Veridata Web Certificates

Prerequisites

• Backup <veridata_install>/config/vdtWebKeystore.p12 outside veridata install location

• The server certificate, private key, and CA certificate must be in PEM format

• Use absolute paths for all certificate files.

• The user running the command must have read permission on the PEM files and write permission to <veridata_install>/config.

• Stop Veridata Server before replacing the Web UI keystore.

To replace Veridata Web certificates

1. Stop Oracle GoldenGate Veridata Server.

2. Back up the existing Web UI keystore:

   cp <veridata_install>/config/vdtWebKeystore.p12 <outside_veridata_config_path>/vdtWebKeystore.p12.bak

3. Change to the Veridata Configuration Assistant script directory:

   cd <veridata_install>/script/vdtca

4. Set the Veridata configuration directory:

   export VERIDATA_CONFIG_DIR=<veridata_install>/config

5. Run the security setup script with the custom certificate files:

   ./setup_veridata_security.sh custom_cert <absolute_path_to_certificate> <absolute_path_to_private_key <absolute_path_to_CA_certificate> <private_key_password>

   Where:

   • <absolute_path_to_certificate> is the server certificate file in PEM format.

   • <absolute_path_to_private_key> is the private key file in PEM format.

   • <absolute_path_to_CA_certificate> is the CA certificate or CA certificate chain file in PEM format.

   • <private_key_password> is the password for the server private key (only needed when private key is encrypted)

   The script updates <veridata_install>/config/vdtWebKeystore.p12, which is the keystore used for Veridata Web SSL.

6. Verify that vdtWebKeystore.p12 was updated:

    ls -l <veridata_install>/config/vdtWebKeystore.p12

7. Start Oracle GoldenGate Veridata Server.

8. Verify Web UI HTTPS access from a browser:

   https://<veridata_host>:<https_port>