Known issues and limitations
The following are known issues and limitations of the Webex Connector integration.
Known limitations
-
Updates made to users that are disabled in WebEx will not be visible in WebEx until they are reenabled.
-
Because of a limitation with PingFederate 8.1 and earlier versions, when configuring two service provider (SP) connections with the same provisioner, the second connection built might 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.
-
User attributes cannot be cleared when set.
-
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.
-
The Webex API does not allow a user to be created in a disabled state. Webex activates all users after creation.
-
The connector cannot re-enable user meeting types that have been disabled through the Webex administration console. If the connector tries to update the user’s meeting types in this scenario, it can cause all meeting types for that user to be disabled.