> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Zscaler Private Access

> Connect your Zscaler Private Access (ZPA) tenant to Oleria to discover your private applications and the access policy rules that open them to identity provider and SCIM groups.

Connect Zscaler Private Access (ZPA) to Oleria to see which private applications your ZPA tenant publishes and which groups its access policy lets reach them. Oleria reads segment groups, application segments, and access policy rules from the ZPA API through Zscaler OneAPI, with an OAuth2 API client from ZIdentity. The integration is read-only: Oleria makes no changes in ZPA.

> [!NOTE]
>
> This page covers **Zscaler Private Access**. For users, administrators, groups, and admin roles in Zscaler Internet Access, see [Zscaler Internet Access](https://docs.oleria.com/integrations/zscaler-internet-access.md). One ZIdentity API client can serve both integrations once it has a role for each product.

## What Oleria discovers

Once connected, Oleria continuously discovers and maps the following from your ZPA tenant:

* **Private applications** - your ZPA tenant, its segment groups, and the application segments in each segment group, with their domains, TCP and UDP port ranges, and whether each is enabled. An application segment with no segment group sits directly under the tenant.
* **Groups** - the identity provider (IdP) and SCIM groups your access policy rules name. A rule that names a whole IdP appears as a group called **All users of** followed by the IdP name.
* **Access** - for each enabled access policy rule, which groups it grants or denies access to which segment groups and application segments. Each access entry records the rule's name, order, and action, plus any other conditions the rule sets, such as posture or client type.
* **Broader rules** - rules that apply to everyone who authenticates, or to users who match a SAML or SCIM attribute rather than a group, are listed on the application they apply to. Allow rules are labeled **openTo** and deny rules **deniedTo**.

ZPA doesn't give an API client its users or group members, so Oleria doesn't discover user accounts or group membership for ZPA. ZPA admin roles, disabled rules, and the default rule aren't synced.

## Prerequisites

* A Zscaler Private Access tenant on a commercial Zscaler cloud. Your organization must use ZIdentity for OneAPI.
* Access to the ZIdentity Admin Portal to create an API client, and to the ZPA Admin Portal to choose or create a ZPA role for it.
* Admin access on the Oleria platform to add a new integration.

### Permissions

The ZPA role on the API client controls what Oleria can read. Zscaler grants each permission group **Full** or **Read Only** access. Read Only is enough, because Oleria makes no changes. See Zscaler's [Configuring Administrator Roles](https://help.zscaler.com/zpa/configuring-administrator-roles).

| ZPA permission | Used for | Required |
| :- | :- | :- |
| Configuration **or** Policies | Segment groups, application segments, and access policy rules. | Yes. Oleria won't connect without read access to all three. |
| SCIM Management **or** Policies | IdP, SCIM group, and attribute names, used to name the groups and conditions in your access rules. | No. Without it, Oleria still connects and syncs, names those groups and conditions by their ID, and marks the sync as partially completed. |

**Read Only** on **Policies** alone covers both rows.

## Create credentials in Zscaler

**1. Choose a ZPA role**

In the ZPA Admin Portal, choose or create a role with the permissions listed in [Permissions](#permissions). A role with **Read Only** on **Policies** works.

**2. Create an API client in ZIdentity**

In the ZIdentity Admin Portal, go to **Administration** -> **API Configuration** -> **OneAPI** -> **API Clients** and select **Add API Client**. Give the client a name such as `Oleria`. An API client you already use for the Zscaler Internet Access integration also works once you give it a ZPA role.

**3. Add a client secret**

Under client authentication, add a **Secret**. Copy the secret: Zscaler shows it only once. Note its expiry date, because you need to update the secret in Oleria before it expires.

**4. Assign the ZPA role**

Under resources, assign the ZPA role from the first step for your ZPA tenant, then select **Save**. Without a ZPA role, the API client's access token doesn't name your ZPA tenant and Oleria can't connect.

**5. Copy the client details**

Copy the API client's **Client ID**. Then note your ZIdentity vanity domain: the part before `.zslogin.net` in your ZIdentity sign-in URL. For example, it's `acme` in `https://acme.zslogin.net`.

## Connect Zscaler Private Access to Oleria

**1. Open the integration**

Go to your Oleria workspace, select **Integrations** -> select **Zscaler Private Access**.

**2. Complete the connection form**

| Field | Notes |
| :- | :- |
| Client ID | Required. The client ID of the ZIdentity API client. |
| Client Secret | Required. The secret you added to the API client. |
| Vanity Domain | Required. Your ZIdentity vanity domain only, for example `acme` - not a full URL. Letters, digits, and hyphens only, with no hyphen at the start or end. |

**3. Authenticate**

Select **Authenticate** to validate and save the integration. Oleria requests an access token, checks that it names a ZPA tenant, then reads one segment group, application segment, access policy rule, and IdP to confirm access. Oleria refuses to connect if it can't read segment groups, application segments, or access policy rules.

> [!NOTE]
>
> When you edit the integration later, you can change only the **Client Secret**. To change the client ID or vanity domain, connect a new instance.

## Verify the integration

Confirm the Zscaler Private Access instance appears on the **Connected** tab of your Oleria **Integrations** page. After the first sync completes, review the discovered segment groups, application segments, and groups in your Oleria workspace.

The integration's capabilities show group and resource reads. Oleria re-checks both on each capability refresh, and marks one not enabled if the API client loses its ZPA role or its read access.

If the sync is marked as partially completed, either the role can't read IdPs and SCIM groups, so some groups are named by their ID, or an access rule names a segment group or application segment that ZPA didn't list. See [Permissions](#permissions) and [Known limitations](#known-limitations).

> [!NOTE]
>
> If you rotate the client secret, update it in Oleria by editing the integration. Discovery stops until you do.

## Known limitations

* **No users or group members.** ZPA doesn't give an API client its users, so Oleria shows which groups can reach an application, not which people are in those groups. Use your identity provider's integration for membership.
* **Oleria shows rules, not effective access.** ZPA applies the first matching rule by rule order, so a deny rule above an allow rule wins. Oleria records each rule's order and action, but doesn't work out which rule wins for a given user.
* **Access to a segment group isn't copied to its applications.** A rule that targets a segment group appears on the segment group, and its application segments sit under it.
* **Rules that need several groups appear on each group.** A rule that requires membership in group A and group B shows access for both groups. Each access entry names the other groups the rule also requires, so a review can see that only users in both get access.
* **Attribute conditions aren't groups.** Rules that match SAML or SCIM attributes appear in the application's **openTo** or **deniedTo** label, with the attribute values, rather than as groups with access.
* **Microtenants.** Oleria reads lists without naming a microtenant. A rule that names a segment group or application segment ZPA didn't list, for example one in a microtenant, gets no access entry, and the sync is marked as partially completed.
* **ZIdentity groups aren't linked across integrations.** Groups that ZPA gets from ZIdentity aren't linked to the same groups in the Zscaler Internet Access integration.
* **Commercial clouds only.** Oleria connects through Zscaler's production OneAPI endpoints. Government and beta clouds aren't supported.

## Troubleshooting

| Error | What it means | What to do |
| :- | :- | :- |
| `this API client has no ZPA access: its OneAPI token names no ZPA tenant` | The API client has no ZPA role. | In ZIdentity, assign a ZPA role to the API client, then authenticate again. |
| `failed to obtain a Zscaler OneAPI access token` | Zscaler didn't issue a token. | Check the vanity domain, client ID, and client secret, and that the API client is active and its secret hasn't expired. |
| `the connection cannot read ZPA segment groups` (or `application segments`, or `access policy rules`) | The ZPA role can't read that list. | Give the role **Read Only** access to **Configuration** or **Policies**. |
| `ZPA reports it not found under the customer id the API client's token names` | The customer ID in the token doesn't exist on this ZPA cloud, or the role is scoped to a microtenant. | Check that the role is for your parent ZPA tenant and that the tenant is on a commercial cloud. |
| `Enter only the vanity domain, such as acme for acme.zslogin.net` | The vanity domain field has a full URL or other characters. | Enter only the label before `.zslogin.net`. |

## Contact us

For questions about this integration, contact us at [support@oleria.com](mailto:support@oleria.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.