- PrivaceraCloud Release 7.4
- Enhancements and updates in PrivaceraCloud release 7.4
- Known Issues in PrivaceraCloud 7.4
- PrivaceraCloud User Guide
- Overview of PrivaceraCloud
- Connect applications with the setup wizard
- Connect applications
- About applications
- Connect Azure Data Lake Storage Gen 2 (ADLS) to PrivaceraCloud
- Connect Amazon Textract to PrivaceraCloud
- Athena
- Privacera Discovery with Cassandra
- Connect Databricks to PrivaceraCloud
- Databricks SQL
- Databricks SQL Overview and Configuration
- Planning and general process
- Prerequisites
- Databricks SQL with Privacera Hive
- Connect Databricks SQL application
- Grant Databricks SQL permissions to PrivaceraCloud users
- Define a resource policy
- Test the policy
- Databricks SQL PolicySync fields
- Configuring column-level access control
- View-based masking functions and row-level filtering
- Create an endpoint in Databricks SQL
- Databricks SQL Fields
- Databricks SQL Hive Service Definition
- Databricks SQL Masking Functions
- Databricks SQL Encryption
- Use a custom policy repository with Databricks
- Connect Databricks SQL to Hive policy repository on PrivaceraCloud
- Databricks SQL Overview and Configuration
- Connect Databricks Unity Catalog to PrivaceraCloud
- Connect S3 to PrivaceraCloud
- Prerequisites in AWS console
- Connect S3 application to PrivaceraCloud
- Enable Privacera Access Management for S3
- Enable Data Discovery for S3
- S3 AWS Commands - Ranger Permission Mapping
- S3
- AWS Access with IAM
- Access AWS S3 buckets from multiple AWS accounts
- Add UserInfo in S3 Requests sent via Dataserver
- Control access to S3 buckets with AWS Lambda function on PrivaceraCloud
- Dremio Plugin
- DynamoDB
- Connect Elastic MapReduce from Amazon application to PrivaceraCloud
- Connect EMR application
- EMR Spark access control types
- PrivaceraCloud configuration
- AWS IAM roles using CloudFormation setup
- Create a security configuration
- Create EMR cluster
- How to configure multiple JSON Web Tokens (JWTs) for EMR
- EMR Native Ranger Integration with PrivaceraCloud
- Connect EMRFS S3 to PrivaceraCloud
- Files
- GBQ
- Google Cloud Storage
- Connect Glue to PrivaceraCloud
- Google BigQuery for PolicySync
- Connect Kinesis to PrivaceraCloud
- Connect Lambda to PrivaceraCloud
- Microsoft SQL Server
- MySQL for Discovery
- Open Source Apache Spark
- Oracle for Discovery
- PostgreSQL
- Connect Power BI to PrivaceraCloud
- Presto
- Redshift
- Snowflake
- Starburst Enterprise with PrivaceraCloud
- Starburst Enterprise Presto
- Trino
- Connect users
- Data access Users, Groups, and Roles
- UserSync
- Portal user LDAP/AD
- Datasource
- Okta Setup for SAML-SSO
- Azure AD setup
- SCIM Server User-Provisioning
- User Management
- Identity
- Access Manager
- Access Manager
- Resource Policies
- Tag Policies
- Scheme Policies
- Service Explorer
- Reports
- Audit
- About data access users, groups, and roles resource policies
- Security zones
- Discovery
- Classifications via random sampling
- Privacera Discovery scan targets
- Propagate Privacera Discovery Tags to Ranger
- Enable offline scanning on Azure Data Lake Storage Gen 2 (ADLS)
- Enable Real-time Scanning of S3 Buckets
- Enable Real-time Scanning on Azure Data Lake Storage Gen 2 (ADLS)
- Enable Discovery Realtime Scanning Using IAM Role
- Encryption
- Overview of Privacera Encryption
- Encryption schemes
- Presentation schemes
- Masking schemes
- Create scheme policies
- Privacera-supplied encryption schemes for the Privacera API
- Privacera-supplied encryption schemes for the Bouncy Castle API
- API date input formats
- Deprecated encryption formats, algorithms, and scopes
- Privacera Encryption REST API
- PEG API endpoint
- PEG REST API encryption endpoints
- Prerequisites
- 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
- Make encryption API calls on behalf of another user
- Privacera Encryption UDF for masking in Databricks on PrivaceraCloud
- Privacera Encryption UDFs for Trino on PrivaceraCloud
- Syntax of Privacera Encryption UDFs for Trino
- Prerequisites for installing Privacera Crypto plug-in for Trino
- Download and install Privacera Crypto jar
- Set variables in Trino etc/crypto.properties
- Restart Trino to register the Privacera encryption and masking UDFs for Trino
- Example queries to verify Privacera-supplied UDFs
- Privacera Encryption UDF for masking in Trino on PrivaceraCloud
- Encryption UDFs for Apache Spark on PrivaceraCloud
- Launch Pad
- Settings
- Dashboard
- Usage statistics
- Operational status of PrivaceraCloud and RSS feed
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- PrivaceraCloud Previews
- Preview: File Explorer for S3
- Preview: File Explorer for Azure
- Preview: File Explorer for GCS
- Preview: Scan Generic Records with NER Model
- Preview: Scan Electronic Health Records with NER Model
- Preview: OneLogin setup for SAML-SSO
- Preview: Azure Active Directory SCIM Server UserSync
- Preview: OneLogin UserSync
- Preview: PingFederate UserSync
- Quickstart for Databricks Unity Catalog on PrivaceraCloud
- What do I need to do in my Databricks Workspace?
- Where is the sample dataset in my Databricks Workspace?
- What should I do in the PrivaceraCloud web portal?
- Access use-case - How do I give a user access to a table or restrict from running a SQL select query?
- Access use-case - How do I restrict a user from seeing contents of a column in the result of a SQL select query?
- Column masking use-case - How do I restrict a user from seeing contents of a column by masking the values in the result of a SQL select query?
- Access use-case - How do I disallow a user from seeing certain rows of a table?
- PrivaceraCloud documentation changelog
UserSync in PrivaceraCloud
UserSync: Data Access Users
This topic describes how to use UserSync in PrivaceraCloud to connect to an external resource (such as LDAP, AD, AAD, SCIM, OKTA, and SCIM Server) for the purpose of connecting, pulling, or serving as data access users.
Connect application
You can connect your application using an existing system or add a new one.
On your system dialog, click the three dots menu and then Add Application.
In the Application List, click USERSYNC.
In the Service Type list, select the connection protocol/service you wish to connect:
LDAP
AD
AAD
SCIM (System for Cross Identity Management - Client)
Okta
SCIM-Server (System for Cross Identity Management - Server Endpoint)
Enter the Connector Name , then click NEXT.
In the BASIC tab, enter the values. See below table:
Property
Example
Service URL
"ldap://dir.privacera.us:389"
Bind DN
"CN=Bind User,OU=privacera,DC=ad,DC=privacera,DC=us"
Bind Password
as needed
Search Base
"DC=ad,DC=privacera,DC=us"
In the ADVANCED tab, the value in the Authentication Type field must be
simple
.To enable paging for UserSync via LDAP:
Select the Incremental Search check box.
In the Add Custom Properties text box, set the following properties:
usersync.connector.results.paged.enabled=true usersync.connector.results.paged.size=<Results_Per_Page>
Click Next.
The configuration wizard will advance you through the configuration pages. Complete and step through each of the pages.
Note
Configure Filters
Azure Active Directory- There are the following optional fields for filtering:
Include Users By Domain: Add domain names to include, default value is empty
Exclude Users By Domain: Add domain names to exclude, default value is empty
Okta- There are the following optional fields for filtering, select either "Equals" or "Starts with". For each of these filters that are defined, all users not included are ignored. Wildcard (*) allowed.
Include Users With Email
Include Users With First Name
Include Users With Last Name
Complete all BASIC values, then review and update ADVANCED values as required.
Click FINISH.
OKTA: Pull data access users and groups from Okta. PrivaceraCloud will use Okta protocols in client-mode to connect to an Okta enabled SCIM-Server. It will synchronize with the targeted server to obtain data access users and groups.
SCIM: Pull data access users and groups from the generic SCIM 2.0 compliant server.
SCIM-SERVER: Configure to allow data access users and groups to be provided (pushed) to your PrivaceraCloud account from a SCIM 2.0 client, including push integration with an Okta Identity Provider. See SCIM Server User-Provisioning for detailed setup instructions.
In the BASIC tab, enter Endpoint URL and Bearer Token.
Click Next.
The configuration wizard will advance you through the configuration pages. Complete and step through each of the pages.
Complete all BASIC values, then review and update ADVANCED values as required.
Click FINISH.
You can use advanced settings to perform a variety of transformations on user-related data from your Identity Provider (IdP).
On the Base User Attributes page, go to the ADVANCED tab.
Then on the Customize Base LDAP Source Attribute Keys dropdown:
Apply to Attribute(s): Specify the names of LDAP attributes to which these customizations apply.
Extract from email: Extract the username portion of an email address value from the username attribute field. The username then becomes the value to the left of the
@-sign
of the email address.Caution
Duplicate usernames map to a single username.
Usernames in email addresses (the left-hand side of the @-sign) that are identical even if they are different domains (the right-hand side of the @-sign) are considered the same user on import.
For example these email addresses with different domains result in the same user on PrivaceraCloud :
BillSmith@gmail.com
BillSmith@yourcompany.com
No Conversion: If you select any of the following conversions, this radio button is unselected.
Convert attribute values to lowercase. Allowable values:
true
orfalse
.Convert attribute values to uppercase. Allowable values:
true
orfalse
.Prefix to Prepend. Allowable values: String to prepend.
Postfix to Append. Allowable values: String to append.
Regex Replace Expression. Allowable values: Substitute any string represented by a regular expression with another string. Requires Linux-editor-style
s
command, with optionalg
for global replacement. Examples:Regexp
s/ch/AAA/g
:ch
(a simple string) is globally replaced withAAA
.Regexp
s/[123]//
: The first occurrence of the number1
or2
or3
is removed.Regexp
s/a[bc]/z/
: The first occurence of the lettera
optionally followed by eitherb
orc
is replaced byz
.