- 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
Apache Ranger API
Each PrivaceraCloud account uses an internal Apache Ranger process to assist with the access control functions. This Apache Ranger process can be accessed directly via its REST API.
The Apache Ranger API is standardized and open source. For the full Ranger API specification, see Apache Ranger API and Apache Ranger Interactive Swagger Ranger API definition.
PrivaceraCloud allows the full use of the Ranger API but disallows modification, removal, or overwrite of itself as the Apache Ranger plug in. The following methods are disallowed and will return an HTTP Status 403 (Access Forbidden):
POST <RangerAdminURL>/service/plugins/definitions
PUT <RangerAdminURL>/service/plugins/definitions
DELETE <RangerAdminURL>/service/plugins/definitions
PrivaceraCloud Apache Ranger API Access
Establish access credentials for Basic Auth authentication.
Create an Admin Data Access User API Service Account

The best practice is to create at least one Ranger API data access service account:
Open Access Manager > Users/Groups/Roles, and create a user.
Set the Role to Admin. Record the password.

Generate a Ranger Admin API URL
Open Settings > ApiKey, and click + Generate Api Key .
In this first Generate Api Key dialog, set the purpose to "REST API Access" or similar and check the Never Expires box.
Click Generate Api Key to proceed to the next dialog.
In the second Generate Api Key dialog, under Ranger Admin URL, click Copy Url, then close the dialog
The Api Key page will display the added Api Key, similar to the following:

Test and Confirm Access
The Ranger Admin URL will look similar to:
https://api.privaceracloud.com/api/13afxxxxxx6b981fxxxxxx2dc7cdd7xxxxxxa921636xxxxxx2d189d425b5f01
A full URL Ranger API service URI is "<RangerAdminURL>/service/<Ranger API Resource Path>".
Example
Using curl and the Ranger API "/plugins/services" method to confirm access, the full curl command is:
curl -u RangerAPI-Auth:ranger1234# https://api.privaceracloud.com/api/13afxxxxxx6b981fxxxxxx2dc7cdd7xxxxxxa921636xxxxxx2d189d425b5f01/service/plugins/services
A typical response would be:
{ "startIndex": 0, "pageSize": 200, "totalCount": 1, "resultSize": 1, "sortType": "asc", "sortBy": "serviceId", "queryTimeMS": 1604017945463, "services": [ { "id": 1, "guid": "8927fc53-4036-44a8-bc12-482d302164fc", "isEnabled": true, "createdBy": "Admin", "updatedBy": "Admin", "createTime": 1603341313000, "updateTime": 1603341313000, "version": 1, "type": "hive", "name": "privacera_hive", "displayName": "privacera_hive", "description": "Hive repo", "configs": { "password": "**", "jdbc.driverClassName": "org.apache.hive.jdbc.HiveDriver", "jdbc.url": "jdbc:hive2://localhost:10000", "username": "hive" }, "policyVersion": 8, "policyUpdateTime": 1603341313000, "tagVersion": 1, "tagUpdateTime": 1603341313000 } ] }