Privacera Platform

Validation

:

Validations are a set of commands/checks that are performed before and after the installation of a Privacera component. Run the validations to ensure that all the pre-installation conditions are satisfied and the services post-installation are up and running with expected functionality. At the end of each check, a validation report is generated giving you the results of the check whether it has passed/failed.

Validations in Privacera Manager are divided into the following two parts, where each of them has its own set of commands/checks. Each part is independent and can be called at any time based on whether it's a pre-installation check or post-installation check.

Pre-installation Validation

The following sections describe validations to perform prior to installation.

pre_check

Checks if all the properties in the configuration YAML files are set correctly or not. If any passwords are used, they are checked as per the password policy.

Command to check for all configured services.

./privacera-manager.sh pre_check

Command to check for a specific service. For example, pre_check portal.

./privacera-manager.sh pre_check [service_tag]
pre_validation

Checks if a connection can be established between a Privacera service and an external service such as an external RDS database, S3, or ADLS. Validations make sure that the network connectivity and credentials specified in properties are working and have proper access to work with required external services.

Command to check for all configured services.

./privacera-manager.sh pre_validation

Command to check for a specific service. For example, pre_validation portal.

./privacera-manager.sh pre_validation [service_tag]

Post-installation validations

service_check

Checks if a Privacera service is up and running. Use this command to check for all configured services.

./privacera-manager.sh service_check

Command to check for a specific service. For example, service_check portal.

./privacera-manager.sh service_check [service_tag]
service_validation

Performs basic sanity checks on the services installed by carrying out some actions. This validates the integrity of the installed services whether they are working properly.

Command to check for all configured services:

./privacera-manager.sh service_validation

Command to check for a specific service. For example, service_validation portal.

./privacera-manager.sh service_validation [service_tag]
security_check

Checks where the Privacera passwords should be stored (JCEKS or vault), checks for default passwords in the configuration files, and validates the SSL certificate installed on the services.

Command to check for all configured services:

./privacera-manager.sh security_check

Command to check for a specific service. For example, security_check portal.

./privacera-manager.sh security_check [service_tag]

Validation reports

Validations reports are stored in the logs directory with the timestamp folder. After a validation run, it shows a validation summary and the path to the directory where all the last validation reports are generated.

The following is the screenshot of service check and it shows the path of the directory where the validation report is stored, also the summary of the service_check, how many of them passed or failed.

Supported validations

The following table contains all the supported validations for each Privacera service: