Disable Access Control¶
Use this setting when you want Privacera to handle data masking only, and you want access control (access management) completely disabled.
When this property is enabled:
- Access management is fully disabled for the MSSQL connector.
- PolicySync loads only masking-related ACLs and does not load access-control ACLs.
- Any access policy you create in the Privacera portal will not work — it will not grant permissions in Microsoft SQL Server.
- Access control must be managed by an external system; Privacera continues to synchronize and apply masking policies.
Default value: false (access-control ACLs are loaded and portal access policies work as usual).
Set to false (or omit the property) to keep access control enabled.
Setup¶
-
SSH to the instance where Privacera Manager is installed.
-
Open the connector variables file:
If you have multiple connectors, replace
instance1with the appropriate connector instance name.Bash -
Add or update the property to disable access control:
YAML -
Run the following commands to update your Privacera Manager platform 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.
-
In the PrivaceraCloud portal, go to Settings → Applications.
-
On Connected Applications, select MSSQL and open the application for edit.
-
Go to Access Management → ADVANCED.
-
Under Add New Custom Properties, add (replace
0with your connector index if needed):Properties -
Select SAVE to apply the changes.
- Prev topic: Advanced Configuration