- 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
The following table contains the list of custom properties that can be configured for the Portal service. To use a custom property from the table, just add it to the following YML file in the custom-vars
folder configured as per your environment:
vars.portal.yml
Property | Description | Values | Default Value |
---|---|---|---|
PORTAL_ENABLE | |||
PORTAL_INSTALL | |||
PORTAL_IMAGE_NAME | |||
PORTAL_IMAGE_TAG | |||
PORTAL_SERVER_MODE | |||
PORTAL_SSL_ENABLE | |||
PORTAL_SSL_SELF_SIGNED | |||
PORTAL_UI_SSO_ENABLE | |||
AAD_SSO_ENABLE | |||
PORTAL_LIQUIBASE_ENABLE | |||
PORTAL_PORT | |||
PORTAL_PROTOCOL | |||
PORTAL_PROTOCOL_URL | |||
PORTAL_PORT_EXTERNAL | Property to change the default port number for Portal. | 6868 | |
PORTAL_SERVICE_NAME | |||
PORTAL_HOST_NAME | |||
PORTAL_SVC_IP | |||
PORTAL_INGRESS_IP | |||
PORTAL_EXTERNAL_HOST | |||
PORTAL_URL | |||
PORTAL_EXTERNAL_URL | |||
PORTAL_INGRESS_URL | |||
PORTAL_URL_IP | |||
SAML_ENTITY_ID | |||
SAML_BASE_URL | |||
SAML_METADATA_FILEPATH | |||
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). | true, false | true |
SAML_EMAIL_ATTRIBUTE | Property to customize the email assertion attribute of SAML. | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name | |
SAML_USERNAME_ATTRIBUTE | Property to customize the username assertion attribute of SAML. | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name | |
SAML_LASTNAME_ATTRIBUTE | Property to customize the lastname assertion attribute of SAML. | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/surname | |
SAML_FIRSTNAME_ATTRIBUTE | Property to customize the firstname assertion attribute of SAML. | http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname | |
PRIVACERA_PORTAL_DATASOURCE_URL | |||
PRIVACERA_PORTAL_DATASOURCE_USERNAME | |||
PRIVACERA_PORTAL_DATASOURCE_PASSWORD | |||
PRIVACERA_PORTAL_DATASOURCE_DRIVER_CLASS_NAME | |||
PRIVACERA_PORTAL_DATASOURCE_DIALECT | |||
PRIVACERA_PORTAL_KEYSTORE_ALIAS | |||
PRIVACERA_PORTAL_KEYSTORE_PASSWORD | |||
PRIVACERA_PORTAL_TRUSTSTORE_PASSWORD | |||
PRIVACERA_PORTAL_RANGER_ADMIN_TRUST_STORE | |||
PRIVACERA_PORTAL_SSL_TRUSTSTORE | |||
PRIVACERA_PORTAL_SSL_TRUSTORETYPE | |||
PRIVACERA_PORTAL_SSL_KEYSTORETYPE | |||
PRIVACERA_PORTAL_KEYSTORE_FILENAME | |||
PRIVACERA_PORTAL_SSL_KEY_STORE | |||
PRIVACERA_PORTAL_RANGER_USER_PASSWORD | |||
PRIVACERA_PORTAL_TOPIC_DYNAMIC_PREFIX | |||
PRIVACERA_PORTAL_SSL_SIGNED_PEM_FULL_CHAIN | |||
PRIVACERA_PORTAL_SSL_SIGNED_PEM_PRIVATE_KEY | |||
PRIVACERA_PORTAL_SSL_PKCS12_PASSWORD | |||
PRIVACERA_PORTAL_SSL_SIGNED_CERT_FORMAT | |||
PRIVACERA_PORTAL_SSL_SIGNED_PKCS12_ALIAS | |||
PRIVACERA_PORTAL_SSL_SIGNED_PKCS12_FILE | |||
PORTAL_PADMIN_DEFAULT_PASSWORD | |||
PORTAL_PADMIN_PASSWORD | |||
PRIVACERA_PORTAL_HIVE_USER_PASSWORD | |||
PRIVACERA_PORTAL_AUTH_TOKEN | |||
PRIVACERA_PORTAL_ATLAS_USER_PASSWORD | |||
PRIVACERA_PORTAL_HOST_HEADER_PREVENTION_ENABLE | Set the property to true to enable Privacera Portal host header prevention. | true | |
PRIVACERA_PORTAL_WHITELIST_HOST | Use this property to add the comma-separated list of allowed hosts. | <HOST_IP>, <HOST_NAME> | |
DATASERVER_SVC_IP | |||
DATASERVER_ENDPOINT_HOSTNAME | |||
PORTAL_LDAP_BIND_PASSWORD | |||
PORTAL_LDAP_ENABLE | |||
PORTAL_LDAP_SSL_ENABLED | |||
PORTAL_LDAP_ADD_ETCHOST | |||
PORTAL_LDAP_IP | |||
PORTAL_LDAP_HOST | |||
PORTAL_LDAP_SSL_PM_GEN_TS | |||
PORTAL_LDAP_SSL_TRUSTSTORE_FILE | |||
PORTAL_LDAP_SSL_TRUSTSTORE_TYPE | |||
PORTAL_LDAP_SSL_TRUSTSTORE_PASSWORD | |||
PORTAL_LDAP_SSL_AUTO_GEN_TRUSTSTORE_FILE | Privacera Manager can create a certificate automatically with a certain name. In this property, give a name for the certificate. | client_ldaps_truststore.cer OR client_ldaps_truststore.jks OR client_ldaps_truststore.p12 | client_ldaps_truststore.cer |
PORTAL_LDAP_SSL_AUTO_GEN_TRUSTSTORE_TYPE | Privacera Manager can create a certificate automatically of a specific type. In this property, give a type for the certificate. | cer, jks, p12 | cer |
PORTAL_SOLR_BASIC_AUTH_ENABLED | |||
PORTAL_SOLR_BASIC_AUTH_USER | |||
PORTAL_SOLR_BASIC_AUTH_PASSWORD | |||
PRIVACERA_ACCESS_REQUEST_MANAGER_PASSWORD | |||
PRIVACERA_ACCESS_REQUEST_MANAGER_USER | |||
PRIVACERA_PORTAL_SECRETS_FILE | |||
PORTAL_ENCRYPT_SECRETS | |||
PRIVACERA_PORTAL_SECRETS_KEYSTORE_PASSWORD | |||
PORTAL_ENCRYPT_PROPS_LIST | |||
AWS_PORTAL_LB_CERTIFICATE_ARN | |||
PORTAL_LB_SSL_CERT | |||
PORTAL_LB_SSL_PORT | |||
PORTAL_LB_TARGET_PORT | |||
PORTAL_LB_BACKEND_PROTOCOL | |||
PORTAL_K8S_PVC_NAME | |||
PORTAL_K8S_PVC_STORAGE_SIZE_MB | |||
PORTAL_K8S_PVC_STORAGE_SIZE | |||
PORTAL_K8S_LOADBALANCER_EXTERNAL | |||
PORTAL_K8S_ANNOTATION_LOADBALANCER_ANNOTATION | |||
PORTAL_K8S_STORAGE_PROVISIONER | |||
PORTAL_K8S_SC_NAME | |||
PORTAL_K8S_PV_ENCRYPTED | |||
PORTAL_K8S_PV_KEY | |||
PORTAL_K8S_CPU_REQUESTS | |||
PORTAL_K8S_CPU_LIMITS | |||
PORTAL_K8S_REPLICAS | |||
PORTAL_HELM_CHART_VERSION | |||
PRIVACERA_PORTAL_DATASERVER_ENABLE_APP_DAO_CREATE | |||
PRIVACERA_PORTAL_DATASERVER_ENABLE | |||
PRIVACERA_PORTAL_DATASERVER_PROXY_HOST | |||
PRIVACERA_PORTAL_DATASERVER_PROXY_PORT | |||
PRIVACERA_PORTAL_DATASERVER_PROXY_PROTOCOL | |||
PRIVACERA_PORTAL_DATASERVER_EXPLORER_PROTOCOL | |||
PRIVACERA_PORTAL_DATASERVER_ADLS_STORAGE_TYPE | |||
PRIVACERA_PORTAL_RANGER_SERVICE_NAME | |||
PRIVACERA_PORTAL_RANGER_CLUSTER_NAME | |||
PRIVACERA_ACCESS_REQUEST_MANAGER_ENABLE | |||
PRIVACERA_ACCESS_REQUEST_MANAGER_PROCESS_KEY | |||
PRIVACERA_ACCESS_REQUEST_MANAGER_PROJECT_ROLES_FILE | |||
PRIVACERA_PORTAL_K8S_HA_ENABLE | |||
PRIVACERA_PORTAL_ELECTION_NODE_PATH | |||
PRIVACERA_PORTAL_ZK_CONNECTION_STRING | |||
PRIVACERA_PORTAL_ELECTION_ZK_RETRY | |||
PRIVACERA_PORTAL_ELECTION_ZK_RETRY_SLEEP_IN_MS | |||
PRIVACERA_PORTAL_ELECTION_RETRY_COUNT | |||
PRIVACERA_PORTAL_ELECTION_RETRY_SLEEP_INTERVAL_SEC | |||
PORTAL_K8S_READINESS_PROBE_DELAY_SECS | Time in seconds to delay the Kubernetes readiness probe for the Portal pod. | 120 | |
PORTAL_K8S_READINESS_PROBE_FAILURE_THRESHOLD | Failure threshold is the number of times Kubernetes will try to perform the readiness probe for the Portal pod. | 6 | |
PORTAL_K8S_READINESS_PROBE_PERIOD_SECS | Time in seconds to perform the Kubernetes readiness probe for the Portal pod. | 30 | |
PORTAL_K8S_LIVENESS_PROBE_DELAY_SECS | Time in seconds to delay the Kubernetes liveness probe for the Portal pod. | 400 | |
PORTAL_K8S_LIVENESS_PROBE_PERIOD_SECS | Time in seconds to perform the Kubernetes liveness probe for the Portal pod. | 30 | |
PORTAL_K8S_LIVENESS_PROBE_FAILURE_THRESHOLD | Failure threshold is the number of times Kubernetes will try to perform the liveness probe for the Portal pod. | 3 | |
PORTAL_K8S_STARTUP_PROBE_ENABLED | Enable the startup probe for the Portal pod. | true, false | false |
PORTAL_K8S_STARTUP_PROBE_PERIOD_SECS | Time in seconds to perform the Kubernetes startup probe for the Portal pod. | 30 | |
PORTAL_K8S_STARTUP_PROBE_DELAY_SECS | Time in seconds to delay the Kubernetes startup probe for the Portal pod. | 400 | |
PORTAL_K8S_STARTUP_PROBE_FAILURE_THRESHOLD | Failure threshold is the number of times Kubernetes will try to perform the startup probe for the Portal pod. | 3 | |
PORTAL_K8S_NETWORKING_LOADBALANCER_IP | |||
PORTAL_K8S_NETWORKING_LOADBALANCER_SOURCE_RANGES | |||
PORTAL_TOPOLOGIES | |||
PORTAL_K8S_SERVICE_ACCOUNT | |||
PORTAL_DATABRICKS_REPORT_ENABLE | Property to enable/disable offline reporting in Databricks. Note: Do not set this property, if a Discovery service is already running in your environment. | true,false | false |
SAML_MAX_AUTH_AGE_SEC | it is the maximum time in seconds that a users is allowed by IDP to be logged in since his initial authentication. The default time is 7889400 seconds (3 months). | 7889400 | |
SAML_RESPONSE_SKEW_SEC | It is the maximum difference between local time and time of the assertion creation which still allows messages to be processed. It determines the maximum difference between the clocks of the IDP and SP machines. | 600 | |
SAML_FORCE_AUTHN | When the property is set to true, IDP is required to re-authenticate a user even if the user has an existing session and not rely on any previous authentication events. | true, false | false |
Memory Variables | |||
PORTAL_HEAP_MIN_MEMORY_MB | Minimum Java Heap memory in MB used by Privacera Portal. For example, PORTAL_HEAP_MIN_MEMORY_MB: "1024" | ||
PORTAL_HEAP_MIN_MEMORY | Minimum Java Heap memory used by Privacera Portal. Setting this value will override PORTAL_HEAP_MIN_MEMORY_MB. For example, PORTAL_HEAP_MIN_MEMORY: "1g" | ||
PORTAL_HEAP_MAX_MEMORY_MB | Maximum Java Heap memory in MB used by Privacera Portal. For example, PORTAL_HEAP_MAX_MEMORY_MB: "1024" | ||
PORTAL_HEAP_MAX_MEMORY | Maximum Java Heap memory used by Privacera Portal. Setting this value will override PORTAL_HEAP_MAX_MEMORY_MB. For example, PORTAL_HEAP_MAX_MEMORY: "1g" | ||
PORTAL_K8S_MEM_REQUESTS_MB | Minimum amount of kubernetes memory in MB to be requested by Privacera Portal. For example, PORTAL_K8S_MEM_REQUESTS_MB: "1024" | ||
PORTAL_K8S_MEM_REQUESTS | Minimum amount of kubernetes memory to be used by Privacera Portal. Setting this value will override PORTAL_K8S_MEM_REQUESTS_MB. For example, PORTAL_K8S_MEM_REQUESTS: "1G" | ||
PORTAL_K8S_MEM_LIMITS_MB | Maximum amount of kubernetes memory in MB to be requested by Privacera Portal. For example, PORTAL_K8S_MEM_LIMITS_MB: "1024" | ||
PORTAL_K8S_MEM_LIMITS | Maximum amount of kubernetes memory to be used by Privacera Portal. Setting this value will override PORTAL_K8S_MEM_LIMITS_MB. For example, PORTAL_K8S_MEM_LIMITS: "1G" | ||
PORTAL_CPU_MIN | Minimum amount of kubernetes CPU to be requested by Privacera Portal. For example, PORTAL_CPU_MIN: "0.5" | ||
PORTAL_CPU_MAX | Maximum amount of kubernetes CPU to be used by Privacera Portal. For example, PORTAL_CPU_MAX: "0.5" |