Incident affecting ODC Portal and ODC Studio

Update timeline

1. investigating Mar 19, 2026, 09:35 AM UTC

   We are currently investigating an issue affecting ODC. Users may experience errors when attempting to log into the ODC Portal and ODC Studio if they use External Identity Provider. Affected users are encountering the error message: "Email verification not supported / Email verification is not supported in the current Identity Provider. (OS-ID-BIZ-40302)". The current workaround is to reactivate the built-in identity provider. Please contact Support if you want to implement this option. Our team is actively working to identify the cause and restore full functionality.

2. investigating Mar 19, 2026, 09:46 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 19, 2026, 11:09 AM UTC

   A solution has been applied by rolling back a recent deployment of Identity Services, and our logs indicate that the errors have ceased. We are still investigating the root cause of this issue.

4. resolved Mar 19, 2026, 11:32 AM UTC

   The incident is now resolved and login to ODC Portal and ODC Studio is operating as expected. The issue, which prevented a subset of users from logging in, was caused by a change intended to strengthen the email verification process. We have resolved the situation by rolling back to a previous version of the services and will perform a root cause analysis to prevent a recurrence in future releases.

5. postmortem Mar 23, 2026, 01:46 PM UTC

   On March 19th, 2026, at approximately 06:43 UTC, an issue was identified affecting ODC, where some users were unable to complete the login process for the ODC Portal and ODC Studio when using external Identity Providers. Affected users encountered an error message stating "Email verification not supported" or were blocked from accessing their accounts because the system could not verify their email addresses via the external provider's claims. The incident was caused by a configuration change intended to strictly enforce email verification from external providers. This change inadvertently bypassed a native fallback verification process that certain users relied upon when their external providers did not share specific verification data. The issue was resolved by 11:00 UTC on March 19th following a rollback to the previous service versions. To prevent recurrence, future updates to this functionality will be implemented via a gradual rollout plan, including additional validation steps to ensure all identity provider configurations are fully supported.