---
title: Known issues and limitations
description: The following are known issues or limitations with the PingID Provisioner.
component: pingid
page_id: pingid:release_notes:pf_pid_connector_known_issues_and_limitations
canonical_url: https://docs.pingidentity.com/integrations/pingid/release_notes/pf_pid_connector_known_issues_and_limitations.html
revdate: August 1, 2024
section_ids:
  known-issues: Known issues
  known-limitations: Known limitations
---

# Known issues and limitations

The following are known issues or limitations with the PingID 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 a limitation in the PingID API, changes made to the user's username are not reflected in the PingOne WebPortal.
