- PrivaceraCloud Release 4.5
- PrivaceraCloud User Guide
- PrivaceraCloud
- What is PrivaceraCloud?
- Getting Started with Privacera Cloud
- User Interface
- Dashboard
- Access Manager
- Discovery
- Usage statistics
- Encryption and Masking
- Privacera Encryption core ideas and terminology
- Encryption Schemes
- Encryption Schemes
- System Encryption Schemes Enabled by Default
- View Encryption Schemes
- Formats, Algorithms, and Scopes
- Record the Names of Schemes in Use and Do Not Delete Them
- System Encryption Schemes Enabled by Default
- Viewing the Encryption Schemes
- Formats, Algorithms, and Scopes
- Record the Names of Schemes in Use and Do Not Delete Them
- Encryption Schemes
- Presentation Schemes
- Masking schemes
- Create scheme policies on PrivaceraCloud
- Encryption formats, algorithms, and scopes
- Deprecated encryption formats, algorithms, and scopes
- PEG REST API on PrivaceraCloud
- PEG API Endpoint
- Request Summary for PrivaceraCloud
- Prerequisites
- Anatomy of a PEG API endpoint on PrivaceraCloud
- About constructing the datalist for /protect
- About deconstructing the response from /unprotect
- Example of data transformation with /unprotect and presentation scheme
- Example PEG REST API endpoints for PrivaceraCloud
- Audit details for PEG REST API accesses
- Make calls on behalf of another user on PrivaceraCloud
- Privacera Encryption UDF for masking in Databricks
- Privacera Encryption UDFs for Trino
- Syntax of Privacera Encryption UDFs for Trino
- Prerequisites for installing Privacera Crypto plug-in for Trino
- Variable values to obtain from Privacera
- Determine required paths to crypto jar and crypto.properties
- Download Privacera Crypto Jar
- Set variables in Trino etc/crypto.properties
- Restart Trino to register the Privacera Crypto UDFs for Trino
- Example queries to verify Privacera-supplied UDFs
- Azure AD setup
- Launch Pad
- Settings
- General functions in PrivaceraCloud settings
- Applications
- About applications
- Azure Data Lake Storage Gen 2 (ADLS)
- Athena
- Privacera Discovery with Cassandra
- Databricks
- Databricks SQL
- Dremio
- DynamoDB
- Elastic MapReduce from Amazon
- EMRFS S3
- Files
- File Explorer for Google Cloud Storage
- Glue
- Google BigQuery
- Kinesis
- Lambda
- Microsoft SQL Server
- MySQL for Discovery
- Open Source Spark
- Oracle for Discovery
- PostgreSQL
- Power BI
- Presto
- Redshift
- Redshift Spectrum
- Kinesis
- Snowflake
- Starburst Enterprise with PrivaceraCloud
- Starburst Enterprise Presto
- Trino
- Datasource
- User Management
- API Key
- About Account
- Statistics
- Help
- Apache Ranger API
- Reference
- Okta Setup for SAML-SSO
- Azure AD setup
- SCIM Server User-Provisioning
- AWS Access with IAM
- Access AWS S3 buckets from multiple AWS accounts
- Add UserInfo in S3 Requests sent via Dataserver
- EMR Native Ranger Integration with PrivaceraCloud
- Spark Properties
- Operational Status
- How-to
- Create CloudFormation Stack
- Enable Real-time Scanning of S3 Buckets
- Enable Discovery Realtime Scanning Using IAM Role
- How to configure multiple JSON Web Tokens (JWTs) for EMR
- Enable offline scanning on Azure Data Lake Storage Gen 2 (ADLS)
- Enable Real-time Scanning on Azure Data Lake Storage Gen 2 (ADLS)
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- PrivaceraCloud
- PrivaceraCloud Previews
- Privacera documentation changelog
Preview: PingFederate UserSync
Currently available as a Preview functionality, PingFederate has two possible Privacera Usersync integrations:
Privacera Usersync - SCIM Server : This requires configuration of PingFederate Outbound provisioning.
Privacera Usersync - SCIM : This requires configuration of PingFederate Inbound provisioning.
Prerequisites
PingFederate Administrator account access with user provisioning enabled.
Privacera Usersync - SCIM Server integration
PingFederate configuration steps
In the pingfederate/bin/run.properties file:
pf.provisioner.mode=STANDALONE
See Configuring outbound provisioning in the PingIdentity documentation.
Notice
“Provision groups with distinguished name” should be set to false.
Privacera Usersync configuration steps
The following Privacera Manager (PM) variable needs to be modified to vars.privacera-usersync.scimserver.yml in config/custom_vars:
SCIM_SERVER_ATTRIBUTE_EMAIL: "emails[type-work].value"
To configure SCIM Server connector, go to Configure Connector and click the Advanced tab.
Include the following properties in the Custom Properties field:
usersync.connector.enable.existing.users.conflict=false usersync.connector.enable.existing.groups.conflict=false
In Base User Attributes, modify Email Address value to:
emails[type-work].value
Privacera Usersync - SCIM integration
Configure a SCIM connector with basic authentication.
PingFederate configuration steps
See Configuring SCIM inbound provisioning in the PingIdentity documentation.
Privacera Usersync configuration steps
The following Privacera Manager (PM) variables need to be added to the vars.privacera-usersync.scim.yml file in config/custom_vars:
SCIM_AUTH_TYPE: “basic” SCIM_AUTH_USERNAME: “{SCIM_USERNAME}” SCIM_AUTH_PASSWORD: “{SCIM_PASSWORD}”
If PingFederate is using a self signed SSL certificate, set:
PRIVACERA_USERSYNC_AUTH_SSL_ENABLED: “true”
Place the certificate in: privacera-manager/config/ssl/custom_certificates
Notice
PrivaceraCloud only supports CA signed SSL certificates
Configure Connector Endpoint URL:
https://<HOST>:9031/pf-scim/v1/Users
For the Bearer Token, set a value (this will not be used, as we will override authentication to basic auth in next step).
Add the following properties under Configure Connector-> Advanced tab -> Custom Properties.
usersync.connector.auth.type=basic usersync.connector.username={SCIM_USERNAME} usersync.connector.password={SCIM_PASSWORD}