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. For solutions, see SaaS provisioner does not remove the user in the Knowledge Base.

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

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

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

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