- 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
Preview: OneLogin setup for SAML-SSO
The PrivaceraCloud portal uses OneLogin's Portal for SAML authentication. OneLogin must be configured with SAML for integration with the PrivaceraCloud portal.
Configure SAML in OneLogin
The following steps describe how to configure SAML in OneLogin application:
Log in to your OneLogin account with Username and Password.
In the top menu bar, click the Applications. and select Applications.
Click the Add App button.
Search for SAML, and then select SAML Custom Connector (Advanced) from the list.
In the Display Name text box, enter the display name (i,e., Privacera Portal SAML), and then click Save.
In the left navigation, click Configuration, and enter the following details in the fields:
Audience(EntityID): privacera-portal
Recipient: https://{yourhostname.com}/SingleSignOnService/receiveResponse
ACS (Consumer) URL Validator: https://{yourhostname.com}/*
Note
The source URL is validated by OneLogin. If the source URL matches the regex expression, we respond to it.
If it does not match, OneLogin logs a warning event and responds to the existing ACS (Consumer) URL value.
Example 4.Consider the ACS (Consumer) URL is https://serviceprovider.com/saml/consume/
A secure ACS (Consumer) URL Validator regular expression is
^https:\/\/serviceprovider\.com\/saml\/consume\/$
^
and$
are an essential anchors in the regular expression.ACS (Consumer) URL: https://{yourhostname.com}/SingleSignOnService/receiveResponse
Single Logout URL: https://{yourhostname.com}/logout
Click Save.
In the left navigation, click Parameters, and then click + icon.
Add the following attribute mapping:
UserID: Username
Note
If the user’s login id is username then there should be no issues. If the user login ID is email. This attribute will be considered as username in the portal. The value is email but the domain name is stripped off to get the username. For example: john.joe@company.com. The username will be considered as john.joe. If there is another attribute which can be used as the username then this value will hold that attribute.
Select the Include in SAML assertion checkbox.
You can also add the following attributes mapping:
EmailAddress: Email
FirstName: FirstName
LastName: LastName
Click Save.
In the top right corner, go to the More Actions drop-down list, and select SAML Metadata.
It will start downloading the XML metadata (i.e.,
onelogin_metadata_{id}.xml
. You can use this XML file in SAML configuration in PrivaceraCloud.
Configure SAML in PrivaceraPortal
On the left navigation, go to Settings > Identity.
Click the Single Sign On section.
You can see the single Sign On section with the fields.
Enter the Application Properties details.
The following table shows the mapping of the fields in PrivaceraCloud with the fields of the SAML app in the OneLogin account:
Table 36. PrivaceraCloud and OneLogin filedsPrivaceraCloud Fields
SAML App Fields in OneLogin
Values
Description
Entity Id
Entity ID
privacera-portal
The value of the entity id is the same as that which is used to configure OneLogin.
Identity Provider Url
SAML 2.0 Endpoint (HTTP)
URL
You can find this URL in: OneLogin SAML Application > SSO > SAML 2.0 Endpoint (HTTP)
Identify Provider Metadata
SAML Metadata
XML file
You get this XML file from: OneLogin > Applications > More Actions > SAML Metadata > onelogin_metadata_{id}.xml
UserNAme Attribute
UserID
Username
Use the same as configured in the OneLogin UserID in Parameters.
Email Attribute
EmailAddress
Email
Use the same as configured in the OneLogin EmailAddress in Parameters. If the name and email address in your OneLogin account are the same, you can use the name instead of the email address.
FirstName Attribute
FirstName
FirstName
Use the same as configured in the OneLogin FirstName in Parameters.
LastName Attribute
LastName
LastName
Use the same as configured in the OneLogin LastName in Parameters.
Click Save.