This article provides instructions on how to configure different vendors with your Policy Orchestration Points (POP). Users will need to modify and add the credential objects as listed in the POP API Documentation according to their preferred vendor. These credentials are acquired from the vendors and are used as parameters in the POP APIs.
Power BI
This section outlines the parameters required for integrating Power BI with your system. It provides a detailed explanation of the general parameters necessary for authentication and access, as well as the optional Discovery Scope Parameters used to customize user permissions and Workspace or Dataset discovery.
General Parameter Table:
Parameter | Description | Value |
---|---|---|
authenticationMethod |
Authentication Method | "service_principal" |
clientID |
Power BI Client ID | string |
clientSecret |
Power BI Client Secret | string |
tenant |
Power BI Tenant ID | string |
discoveryScopeRule |
Optional parameter that allows users to specify user permissions and definitions during Discovery based on Workspaces and Datasets. See the Discovery Scope Parameter Table below for specific parameter information. |
JSON Array |
Discovery Scope Parameter Table:
Parameter | Description | Value |
---|---|---|
hierarchyScopeKey |
Defines where the Discovery is based Valid values: - workspace - dataset |
string |
operator |
Defines the operator for the Discovery. Valid Values: - IN - NOT_IN - EQUALS - NOTEQUALS |
string |
value |
Specifies the name of the Workspace or Dataset on which the Discovery is based. When using a Dataset, ensure it is formatted as follows, with the Workspace name: ["workspace.dataset"] |
array |
Power BI Credentials Examples
Workspace Example:
...
{
"popConnectionCredentials": {
"authenticationMethod": "service_principal",
"credentials": {
"clientID": "84f8n492-f2ce-446b-bace-6df750c2e8c9",
"clientSecret": null,
"tenant": "0d417611-5b17-425e-a5b9-7b98e1aa24b8",
"discoveryScopeRule": {
"OR": [
{
"AND": [
{
"hierarchyScopeKey": "workspace",
"operator": "EQUALS",
"value": ["workspace1"]
}
]
}
]
}
}
}
}
...
Dataset Example
...
{
"popConnectionCredentials": {
"authenticationMethod": "service_principal",
"credentials": {
"clientID": "84f8n492-f2ce-446b-bace-6df750c2e8c9",
"clientSecret": null,
"tenant": "0d417611-5b17-425e-a5b9-7b98e1aa24b8",
"discoveryScopeRule": {
"OR": [
{
"AND": [
{
"hierarchyScopeKey": "dataset",
"operator": "EQUALS",
"value": ["workspace.dataset"]
}
]
}
]
}
}
}
}
...
Zscaler
Parameter | Description | Value |
---|---|---|
authenticationMethod |
Authentication Method | "client_credentials" |
API Key |
Zscaler API Key | string |
API Key Secret |
Zscaler API Secret | string |
Customer ID |
Zscaler Customer ID | string |
Customer based URI |
Zscaler URI | string |
Zscaler Credentials Example
...
"popConnectionCredentials": {
"authenticationMethod": "client_credentials",
"credentials": {
"API Key": "NzIwNTkwMjQyNjIwMzc1Nzg0OTIwOGFjMmUtYjE1OS00NDg4LTllZmQtYTExY2IzZjI0ZWIw",
"API Key Secret": null,
"Customer ID": "72059024269137504",
"Customer based URI": "https://config.zpabeta.net"
}
},
...
Snowflake
Parameter | Description | Value |
---|---|---|
authenticationMethod |
Authentication Method | "basic_authentication" |
computeWarehouse |
Compute Warehouse | string |
username |
Snowflake Account Username | string |
password |
Snowflake Account Password | string |
port |
Snowflake Server Port | integer |
server |
Snowflake Account Server | string |
Snowflake Credentials Example
...
"popConnectionCredentials": {
"authenticationMethod": "basic_authentication",
"credentials": {
"computeWarehouse": "compute_wh",
"password": null,
"port": 443,
"server": "en14622.us-central-99.snowflakecomputing.com",
"username": "username_1"
}
}
...