- Platform Release 6.5
- Privacera Platform Release 6.5
- Enhancements and updates in Privacera Access Management 6.5 release
- Enhancements and updates in Privacera Discovery 6.5 release
- Enhancements and updates in Privacera Encryption 6.5 release
- Deprecation of older version of PolicySync
- Upgrade Prerequisites
- Supported versions of third-party systems
- Documentation changelog
- Known Issues 6.5
- Platform - Supported Versions of Third-Party Systems
- Platform Support Policy and End-of-Support Dates
- Privacera Platform Release 6.5
- Privacera Platform Installation
- About Privacera Manager (PM)
- Install overview
- Prerequisites
- Installation
- Default services configuration
- Component services configurations
- Access Management
- Data Server
- UserSync
- Privacera Plugin
- Databricks
- Spark standalone
- Spark on EKS
- Portal SSO with PingFederate
- Trino Open Source
- Dremio
- AWS EMR
- AWS EMR with Native Apache Ranger
- GCP Dataproc
- Starburst Enterprise
- Privacera services (Data Assets)
- Audit Fluentd
- Grafana
- Ranger Tagsync
- Discovery
- Encryption & Masking
- Privacera Encryption Gateway (PEG) and Cryptography with Ranger KMS
- AWS S3 bucket encryption
- Ranger KMS
- AuthZ / AuthN
- Security
- Access Management
- Reference - Custom Properties
- Validation
- Additional Privacera Manager configurations
- Upgrade Privacera Manager
- Troubleshooting
- How to validate installation
- Possible Errors and Solutions in Privacera Manager
- Unable to Connect to Docker
- Terminate Installation
- 6.5 Platform Installation fails with invalid apiVersion
- Ansible Kubernetes Module does not load
- Unable to connect to Kubernetes Cluster
- Common Errors/Warnings in YAML Config Files
- Delete old unused Privacera Docker images
- Unable to debug error for an Ansible task
- Unable to upgrade from 4.x to 5.x or 6.x due to Zookeeper snapshot issue
- Storage issue in Privacera UserSync & PolicySync
- Permission Denied Errors in PM Docker Installation
- Unable to initialize the Discovery Kubernetes pod
- Portal service
- Grafana service
- Audit server
- Audit Fluentd
- Privacera Plugin
- How-to
- Appendix
- AWS topics
- AWS CLI
- AWS IAM
- Configure S3 for real-time scanning
- Install Docker and Docker compose (AWS-Linux-RHEL)
- AWS S3 MinIO quick setup
- Cross account IAM role for Databricks
- Integrate Privacera services in separate VPC
- Securely access S3 buckets ssing IAM roles
- Multiple AWS account support in Dataserver using Databricks
- Multiple AWS S3 IAM role support in Dataserver
- Azure topics
- GCP topics
- Kubernetes
- Microsoft SQL topics
- Snowflake configuration for PolicySync
- Create Azure resources
- Databricks
- Spark Plug-in
- Azure key vault
- Add custom properties
- Migrate Ranger KMS master key
- IAM policy for AWS controller
- Customize topic and table names
- Configure SSL for Privacera
- Configure Real-time scan across projects in GCP
- Upload custom SSL certificates
- Deployment size
- Service-level system properties
- PrestoSQL standalone installation
- AWS topics
- Privacera Platform User Guide
- Introduction to Privacera Platform
- Settings
- Data inventory
- Token generator
- System configuration
- Diagnostics
- Notifications
- How-to
- Privacera Discovery User Guide
- What is Discovery?
- Discovery Dashboard
- Scan Techniques
- Processing order of scan techniques
- Add and scan resources in a data source
- Start or cancel a scan
- Tags
- Dictionaries
- Patterns
- Scan status
- Data zone movement
- Models
- Disallowed Tags policy
- Rules
- Types of rules
- Example rules and classifications
- Create a structured rule
- Create an unstructured rule
- Create a rule mapping
- Export rules and mappings
- Import rules and mappings
- Post-processing in real-time and offline scans
- Enable post-processing
- Example of post-processing rules on tags
- List of structured rules
- Supported scan file formats
- Data Source Scanning
- Data Inventory
- TagSync using Apache Ranger
- Compliance Workflow
- Data zones and workflow policies
- Workflow Policies
- Alerts Dashboard
- Data Zone Dashboard
- Data zone movement
- Workflow policy use case example
- Discovery Health Check
- Reports
- How-to
- Privacera Encryption Guide
- Overview of Privacera Encryption
- Install Privacera Encryption
- Encryption Key Management
- Schemes
- Encryption with PEG REST API
- Privacera Encryption REST API
- PEG API endpoint
- PEG REST API encryption endpoints
- PEG REST API authentication methods on Privacera Platform
- Common PEG REST API fields
- Construct the datalist for the /protect endpoint
- Deconstruct the response from the /unprotect endpoint
- Example data transformation with the /unprotect endpoint and presentation scheme
- Example PEG API endpoints
- /authenticate
- /protect with encryption scheme
- /protect with masking scheme
- /protect with both encryption and masking schemes
- /unprotect without presentation scheme
- /unprotect with presentation scheme
- /unprotect with masking scheme
- REST API response partial success on bulk operations
- Audit details for PEG REST API accesses
- Make encryption API calls on behalf of another user
- Troubleshoot REST API Issues on Privacera Platform
- Privacera Encryption REST API
- Encryption with Databricks, Hive, Streamsets, Trino
- Databricks UDFs for encryption and masking on PrivaceraPlatform
- Hive UDFs for encryption on Privacera Platform
- StreamSets Data Collector (SDC) and Privacera Encryption on Privacera Platform
- Trino UDFs for encryption and masking on Privacera Platform
- Privacera Access Management User Guide
- Privacera Access Management
- How Polices are evaluated
- Resource policies
- Policies overview
- Creating Resource Based Policies
- Configure Policy with Attribute-Based Access Control
- Configuring Policy with Conditional Masking
- Tag Policies
- Entitlement
- Service Explorer
- Users, groups, and roles
- Permissions
- Reports
- Audit
- Security Zone
- Access Control using APIs
- AWS User Guide
- Overview of Privacera on AWS
- Configure policies for AWS services
- Using Athena with data access server
- Using DynamoDB with data access server
- Databricks access manager policy
- Accessing Kinesis with data access server
- Accessing Firehose with Data Access Server
- EMR user guide
- AWS S3 bucket encryption
- Getting started with Minio
- Plugins
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- Privacera Platform documentation changelog
Portal SSO with AAD using SAML
Privacera supports SAML that allows you to authenticate users using single-sign on (SSO) technology. It is way to provide access to use Privacera services.
Using the Azure Active Directory (AAD) SAML Toolkit, you can set up single sign-on (SSO) in Privacera Manager for Active Directory users. After setting up the SSO, you will be provided with an SSO button on the login page of Privacera Portal.
Prerequisites
To configure SSO with Azure Active Directory, you need to configure and enable SSL for the Privacera Portal. See Enable CA Signed Certificates or Enable Self Signed Certificates.
Configuring SAML in Azure AD
The following steps describe how to configure SAML in Azure AD application:
Log in to Azure portal.
On the left navigation pane, select the Azure Active Directory service.
Navigate to Enterprise Applications and then select All Applications.
To add a new application, select New application.
Note
If you have an existing Azure AD SAML Toolkit application, select it, and then go to step 8 to continue with the rest of the configuration.
in the search box.Azure AD SAML Toolkit In the Add from the gallery section, type Do the following:
Select Azure AD SAML Toolkit from the results panel and then add the app.
On the Azure AD SAML Toolkit application integration page, in the Manage section and select single sign-on.
On the Select a single sign-on method page, select SAML.
Click the pen icon for Basic SAML Configuration to edit the settings.
On the Basic SAML Configuration page, enter the values for the following fields, and then click Save. You can assign a unique name for the Entity ID.
Entity ID = privacera-portal
Reply URL = https://${APP_HOSTNAME}:6868/saml/SSO
Sign-on URL = https://${APP_HOSTNAME}:6868/login.html
In the SAML Signing Certificate section, find Federation Metadata XML and select Download to download the certificate and save it on your virtual machine.
On the Set up Azure AD SAML Toolkit section, copy the Azure AD Identifier URL.
In the Manage section and select Users and groups.
In the Users and groups dialog, select the user or user group who should be allowed to log in with SSO, then click the Select.
CLI configuration
SSH to the instance where Privacera is installed.
Run the following command:
cd ~/privacera/privacera-manager/ cp config/sample-vars/vars.portal.saml.aad.yml config/custom-vars/
Edit the
vars.portal.saml.aad.yml
file.vi config/custom-vars/vars.portal.saml.aad.yml
Modify the SAML_ENTITY_ID. You need to assign the value of the Entity ID achieved in the above section. For property details and description, refer to the Configuration Properties below.
SAML_ENTITY_ID: "privacera-portal" SAML_BASE_URL: "https://{{app_hostname}}:6868" PORTAL_UI_SSO_ENABLE: "true" PORTAL_UI_SSO_URL: "saml/login" PORTAL_UI_SSO_BUTTON_LABEL: "Azure AD Login" AAD_SSO_ENABLE: "true"
Rename the downloaded Federation Metadata XML file as
privacera-portal-aad-saml.xml.
Copy this file to the~/privacera/privacera-manager/ansible/privacera-docker/roles/templates/custom
folder.Run the following command:
cd ~/privacera/privacera-manager/ ./privacera-manager.sh update
If you are configuring the SSL in an Azure Kubernetes environment, then run the following command.
./privacera-manager.sh restart portal
Configuration properties
Property | Description | Example |
---|---|---|
AAD_SSO_ENABLE | Enabled by default. | |
SAML_ENTITY_ID | Get the value from the Prerequisites section. | privacera-portal |
SAML_BASE_URL | https://{{app_hostname}}:6868 | |
PORTAL_UI_SSO_BUTTON_LABEL | Azure AD Login | |
PORTAL_UI_SSO_URL | saml/login | |
SAML_GLOBAL_LOGOUT | Enabled by default. The global logout for SAML is enabled. Once a logout is initiated, all the sessions you've accessed from the browser would be terminated from the Identity Provider (IDP). | |
META_DATA_XML | Browse and select the Federation Metadata XML, which you downloaded in the Prerequisites section. |
Validation
Go to the login page of the Privacera Portal. You will see the Azure AD Login button.
Configure SAML assertion attributes
By default, the following assertion attributes are configured with pre-defined values:
Email
Username
Firstname
Lastname
You can customize the values for the assertion attributes. To do that, do the following:
Run the following commands.
cd ~/privacera/privacera-manager/ cp config/sample-vars/vars.portal.yml config/custom-vars/ vi config/custom-vars/vars.portal.yml
Add the following properties and assign your values. For more information on custom properties and its values, click here.
SAML_EMAIL_ATTRIBUTE: "" SAML_USERNAME_ATTRIBUTE: "" SAML_LASTNAME_ATTRIBUTE: "" SAML_FIRSTNAME_ATTRIBUTE: ""
Add the properties in the YAML file configured in the Configuration above.
cd ~/privacera/privacera-manager/ ./privacera-manager.sh update