---
title: Known issues and limitations
description: The following are known issues or limitations with the Zscaler Private Access Provisioner.
component: zscaler
page_id: zscaler:zscaler_private_access_provisioner:pf_zscaler_zpa_connector_known_issues_and_limitations
canonical_url: https://docs.pingidentity.com/integrations/zscaler/zscaler_private_access_provisioner/pf_zscaler_zpa_connector_known_issues_and_limitations.html
llms_txt: https://docs.pingidentity.com/integrations/zscaler/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: June 18, 2024
section_ids:
  known-issues: Known issues
  known-limitations: Known limitations
---

# Known issues and limitations

The following are known issues or limitations with the Zscaler Private Access Provisioner.

## Known issues

There are no known issues.

## Known limitations

* When an LDAP user is deleted in a targeted group distinguished name (DN), the provisioning connector does not propagate the deletion until a new user is added to the group. This limitation is compounded when the **User Create** provisioning option is disabled. For solutions, see [SaaS provisioner does not remove the user](https://support.pingidentity.com/s/article/After-deleting-an-AD-user-account-SaaS-provisioner-does-not-remove-the-user-in-the-next-provisioning-cycle-when-Group-DN-is-specified) in the Knowledge Base.

* Due to PingFederate limitations, user attributes cannot be cleared once set.

* Due to PingFederate limitations, the Group name is the only supported group attribute and must be the Common Name (CN) of the LDAP Group being provisioned. Additional group attributes are not supported in PingFederate.

* Performance

  * Zscaler SCIM servers have a rate limit of 5 requests per second. In order to avoid retries, reduce the number of threads in the PingFederate channel configuration. For more information, see [Specifying channel information](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/help_saaschanneltasklet_saasgeneralinfostate.html) in the PingFederate documentation and [SCIM API Examples](https://help.zscaler.com/zia/scim-api-examples) in the Zscaler documentation.

  * When provisioning users to a group, all users must be set to active. If an inactive user is present, the active users and group will be provisioned but no users will be added to the group.

  * Rate limiting can prevent the connector from provisioning users to groups. If rate limiting forces a retry, and a user is created on the retry, the user's group memberships are applied the next time the relevant groups are updated.
