---
title: Known issues and limitations
description: The following are known issues or limitations with the PingOne Integration Kit.
component: pingone
page_id: pingone:pingone_integration_kit:pf_p1_ik_known_issues_and_limitations
canonical_url: https://docs.pingidentity.com/integrations/pingone/pingone_integration_kit/pf_p1_ik_known_issues_and_limitations.html
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 PingOne Integration Kit.

## Known issues

Provisioning connector

* After upgrading to version 2.2 of the PingOne Connector, using the administrative API to bulk import an earlier version of the PingOne Connector causes an error. Re-create the connection manually.

## Known limitations

Provisioning connector

* When an LDAP user is deleted in a targeted Group 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. Learn more about solutions in [SaaS provisioning connector 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 limitations in PingFederate, user attributes cannot be cleared after they are set.

* PingOne Authentication Policies configuration does not apply for the PCV credential because the PCV management uses user management API.