Update System Database and Privacera Portal Datasource Password¶
When you update the internal user password for the "privacera" user in MariaDB, you must also update the corresponding password in the Privacera Portal configuration. The Privacera Portal uses this password to connect to MariaDB, and if the passwords do not match, the Portal will be unable to establish database connections, resulting in service failures.
Steps¶
Step 1: SSH into Privacera Instance¶
SSH into the instance where Privacera is installed.
Step 2: Get All Pods Details¶
Get the list of all pods in your namespace:
| Bash | |
|---|---|
Step 3: Access MariaDB Pod Shell¶
Go inside the MariaDB pod shell:
| Bash | |
|---|---|
Replace mariadb-pod-name with the actual name of your MariaDB pod from Step 2.
Step 4: Update Internal User Password¶
Login with the root user and password, then update the internal "privacera" user password:
| SQL | |
|---|---|
Replace <new-password> with your desired new password.
Step 5: Verify Login with New Password and Exit¶
Test the login with the new password and internal user "privacera":
| Bash | |
|---|---|
Enter the new password when prompted. If login is successful, exit from both the MariaDB client session and the pod:
Step 6: Update Privacera Portal Datasource Password¶
Edit the Privacera Portal configuration file:
| Bash | |
|---|---|
Update the PRIVACERA_PORTAL_DATASOURCE_PASSWORD value with your new password:
| YAML | |
|---|---|
Step 7: Update the Instance¶
Step 1 - Setup which generates the helm charts. This step usually takes few minutes.
Step 2 - Apply the Privacera Manager helm charts. Step 3 - (Optional) Post-installation step which generates Plugin tar ball, updates Route 53 DNS and so on. This step is not required if you are updating only connector properties.- Previous: Advanced Configuration