---
title: Known issues and limitations
description: Due to a limitation with PingFederate 8.1 and earlier versions, when configuring two SP connections with the same provisioner, the second connection built may be pre-populated with the channel from the first connection. To avoid conflicts, delete this pre-populated channel and create a unique channel for each connection.
component: evernote
page_id: evernote:release_notes:pf_evernote_connector_known_issues_and_limitations
canonical_url: https://docs.pingidentity.com/integrations/evernote/release_notes/pf_evernote_connector_known_issues_and_limitations.html
revdate: June 11, 2024
---

# Known issues and limitations

* Due to a limitation with PingFederate 8.1 and earlier versions, when configuring two SP connections with the same provisioner, the second connection built may be pre-populated with the channel from the first connection. To avoid conflicts, delete this pre-populated channel and create a unique channel for each connection.

* 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. Learn more in [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 Ping Identity Knowledge Base.

* Due to PingFederate limitations, user attributes cannot be cleared after they're set.

* Provisioning disabled users from the User Store (LDAP) to Evernote is not supported.

* Due to Evernote API limitations, after a user is deactivated, they cannot be reactivated with the provisioner. A deactivated user can only be reactivated in the Evernote Teams Admin Console.

* Due to Evernote API limitations, new users cannot be created with the same username as a previously deactivated user.