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.

Due to an issue that has been reported to the service provider, users that have had their authType set to 'sso' will no longer be able to log in with their standard username and password.

Due to an issue that has been reported to the service provider, the service provider returns an HTTP status code of 500 on some requests to update a user.

Due to a limitation with the service provider’s API, a user’s role can only be updated through the service provider’s administrative console.

Due to Egnyte API limitations, API calls are rate limited. This will prevent requests from being completed. For more information, see Frequently Asked Questions on the Egnyte developers site.