Manual decryption of person data

As of version 8.24.00, the encryption of person data in the database is not supported. During an update from older VTS version to newer versions, the data in the database must be decrypted. When the VTS is updated, the VTS installation program automatically decrypts the candidate data if it is encrypted in the database. You can also run the “CandidateDecryptionTool” manually from the command line before launching the VTS Setup Installer.

Prerequisites

The decryption tool is provided in the installation package via the following path:

“~\CW83000\Tools\CandidateDecryptionTool\CandidateDecryptionTool.exe”.

  • Stop the WTS Service before executing the program.

  • The license dongle for a client/environment must be plugged into the computer or available via the local Sentinel server.

Do not restart the WTS Service after you executed the program, because it will encrypt the data again!

Running the tool

To run the decryption tool, open the command line (cmd), and change the directory to the folder where the tool is located. Then enter the name of the tool CandidateDecryptionTool.exe. Below you’ll find a table of input parameters for the tool:

Parameter

Value

Description

  • [connectionstring | c]

string

Database connection string in MS SQL format e.g.:

“Server=<hostname>\WTSNXEXPRESS;Initial Catalog=wts;Persist Security Info=False;User ID=wtsnx;Password=<password>;

MultipleActiveResultSets=False;Encrypt=False;TrustServerCertificate=False;Connection Timeout=30;"

Example

CandidateDecryptionTool.exe -c "Server=TestSetupEnv-ms \WTSNXEXPRESS;Initial Catalog=wts;Persist Security Info=False;User ID=wtsnx;Password=<password>;MultipleActiveResultSets=False;Encrypt=False;TrustServerCertificate=False;Connection Timeout=30;"

Logging

The CandidateDecryptionTool does not provide any progress information. The progress and result of the decryption process can be reviewed via the log file using the following path: “C:\Users\<username>\AppData\Local\Temp\CandidateDecryptionTool\ CandidateDecryptionTool.log”