Privacera TagSync in the D2P environment¶

Overview¶

Support for Privacera TagSync in the D2P environment allows TagSync to authenticate to Ranger through Privacera Manager configuration, so tag synchronization from Privacera to Ranger works correctly in D2P setups.

• Introduced support for Privacera TagSync in the D2P environment.
• Enables successful synchronization of tags from Privacera to Ranger in D2P configurations.
• TagSync can authenticate with Ranger using credentials supplied in Privacera Manager.

Why this configuration is required¶

In some D2P environments, the Ranger user name for TagSync could be present in properties, but the password was not exposed in Privacera Manager or in site.xml. Without the password, Ranger TagSync cannot connect to Ranger, and authentication errors may appear in the TagSync logs. Setting TAGSYNC_TAG_DEST_RANGER_USERNAME and TAGSYNC_TAG_DEST_RANGER_PASSWORD in vars.ranger-tagsync.yml makes the password available to TagSync the same way other PM-driven settings are applied.

Configure Ranger credentials for TagSync¶

1. SSH into the instance where Privacera Manager is installed.
2. Go to the privacera-manager directory:

1

cd ~/privacera/privacera-manager/

1. Copy the sample variables file if you have not already (the -n flag avoids overwriting an existing file):

1

cp -n config/sample-vars/vars.ranger-tagsync.yml config/custom-vars/

1. Open the custom file for editing:

1

vi config/custom-vars/vars.ranger-tagsync.yml

1. Set the following properties:

1
2

TAGSYNC_TAG_DEST_RANGER_USERNAME: "<your_pcloud_ranger_user>"
TAGSYNC_TAG_DEST_RANGER_PASSWORD: "<password_set_when_creating_pcloud_user>"

1. Once the properties are configured, update your Privacera Manager platform instance by following the

   Bash
   1 2 3	cd ~/privacera/privacera-manager ./privacera-manager.sh setup ./pm_with_helm.sh upgrade