Okta experienced a major incident on November 19, 2024 affecting okta-emea.com cell 1 and okta.com cell 1 and 1 more component, lasting 294d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Nov 19, 2024, 07:56 PM UTC
At 8:40am on November 19th PST, the OIN team became aware of an Import issue with the Paylocity OIN integration affecting customers on all cells of the Okta Workforce Identity Cloud environment. During this time customers may experience import roadblocks. Okta recommends not running imports from Paylocity during this investigation. Okta Engineering is investigating and working to resolve this as quickly as possible. We’ll provide an update in 30 minutes, or sooner if additional information becomes available.
- resolved Nov 19, 2024, 08:27 PM UTC
At 8:40am on November 19th PST, the OIN team became aware of an Import issue with the Paylocity OIN integration affecting customers on all cells of the Okta Workforce Identity Cloud environment. During this time customers may experience import roadblocks. Okta recommends not running imports from Paylocity during this investigation. Okta Engineering has contacted Paylocity and is working to resolve this as quickly as possible. We’ll provide an update in 60 minutes, or sooner if additional information becomes available.
- resolved Nov 19, 2024, 09:22 PM UTC
Okta Engineering has received confirmation from Paylocity that this issue is resolved and is monitoring our backend logging for the Paylocity OIN integration. Our logging indicates an improvement in import success rates. At this time, customers should resume Paylocity imports.
- resolved Nov 19, 2024, 09:36 PM UTC
The Paylocity OIN integration import issue for all Okta Cells have been addressed. Our monitoring shows a return to normal conditions, and we will continue to monitor Paylocity OIN integration import performance. Additional root cause information will be available within 5 Business days.
- resolved Nov 25, 2024, 11:05 PM UTC
Detection: Customers began reporting that Paylocity OIN Integration imports were removing users from Okta. The import jobs were receiving an error response from the Paylocity SCIM API backend. Impact: Paylocity OIN Integration import jobs would receive an error from the Paylocity backend which would then cause the import job to remove users as not found if Paylocity was configured as the profile master. Root Cause: Paylocity confirmed they had erroneously disabled the SCIM API that the Okta integration relies on. This API was disabled between 7:53 AM PST and 1:00 PM PST. Remediation Steps: Okta customers using the Paylocity OIN Integration would need to rerun any imports that occurred during this time window to restore users that had been removed. Import roadblock settings in Okta would prevent excessive removals if configured.