Okta incident
Sign-in Widget (SIW) issue when using embedded Internet Explorer
Okta experienced a minor incident on September 17, 2024 affecting okta-emea.com cell 1 and okta.com cell 1 and 1 more component, lasting 358d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- resolved Sep 17, 2024, 06:20 PM UTC
At 10:00 AM PDT on September 17, 2024, our engineering team became aware of an issue impacting the Okta Sign-in Widget (SIW) for some end users using an embedded Internet Explorer browser. During this time, the end user may experience a popup message that says, "An error has occurred in the script on this page." Our engineering has reverted the change, and we are in the process of confirming the resolution.
- resolved Sep 17, 2024, 06:31 PM UTC
An issue impacting the Okta Sign-in Widget (SIW) for some end users using an embedded Internet Explorer browser has been resolved. Our engineering team has confirmed the resolution. Additional root cause information will be available within 5 Business days.
- resolved Sep 24, 2024, 12:04 AM UTC
We sincerely apologize for any impact this incident has caused you, your business, and your customers. At Okta, trust and transparency are our top priorities. The facts regarding this incident are outlined below. We are committed to implementing improvements to the service to prevent future occurrences of this incident. Detection and Impact On September 16th at 11:57 AM PT, Okta was alerted that a few customers using embedded legacy browsers encountered a Javascript error when logging in. Users were presented with a pop-up window displaying a script error and asked if they would like to continue running scripts. When selecting ‘Yes,’ the page would continue to load correctly. Root Cause Summary A monitoring enhancement to detect client side errors was rolled out, however the library contained modern syntax, which was unrecognized by legacy browsers, resulting in a JS syntax error. Remediation Steps The monitoring enhancement was rolled out at 10:31 AM PT on September 16th. On September 17th, Okta Engineering began rolling back the monitoring changes. The root cause of the issue was identified at 9:42 AM PT. Okta confirmed at 11:17 AM PT that the errors were no longer being observed. Preventative Actions Okta is reviewing and updating our runbooks, improving support case escalation processes to decrease response and resolution times. Additional changes to our rollout processes to mitigate risk are also being applied. Duration (# of minutes): 1495 minutes