← Back to Okta History
unknown✓ Resolved
Resolved Feature Disruption
Status
resolved
Duration
Duration unavailable
Updates
1
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
resolved
Okta customers in all cells that leverage Zoom’s integration for provisioning are experiencing errors while updating users in Zoom. We are actively working with Zoom to identify the root cause and identify a solution.
Resolved: An issue impacting user provisioning updates to the Zoom application within Okta has been resolved. During the event, user updates to the Zoom application may have encountered errors if the provisioned user already existed within Zoom. Okta worked with Zoom to identify the root cause of the issue and applied a hot-fix to all production cells to mitigate the provisioning errors while Zoom worked to deploy a permanent fix. Additional root cause information will be provided within 48 business hours.
Root Cause Analysis: On Nov 19th at approximately 8:53AM PDT, customers reported Zoom provisioning errors when updating user’s profiles.
Upon investigation, Okta determined that the issue was caused by a change in the behavior of an existing Zoom Provisioning API which was introduced on November 17. This change was implemented by Zoom to enable support for changing user's email addresses through the Profile Update request. The change inadvertently caused profile updates to fail, whenever the email has not been changed.
On Nov 19th at approximately 8:17 PM PDT Okta released a work around to address the issue. This update was deployed to all production cells and service was fully restored.
Okta is working closely with Zoom for a fix, as well as, understanding and mitigating the re-occurrence for this type of failure
📊 TECHNICAL DETAILS
Internal ID
b3dc1c94-1bef-4343-856a-3dbd3dfd4cbb
External ID
https://www.salesforce.com/a9C1Y0000004E4EUAU
🕐 First reported
🔄 Last Updated
✓ Resolved
UNKNOWN
Impact Level
Duration unavailable
Total Duration
1
Recorded Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed