✅ (RESOLVED) Apr. 25/23 - 8:30am ET - Incident affecting Wicket SSO

Ryan Knuth
Ryan Knuth
  • Updated

3:30pm ET - Our team has reviewed the incident and discovered the following:

  • At approximately 6:00am ET Apr. 25/23 a service used for delivering configuration for third-party access to Wicket's SSO stopped responding. This resulted in integrations using Wicket's SSO were no longer authorized. The Wicket admin panel login remained functional.
  • SSO service was restored at approximately 9:00am ET.
  • We are currently working with our server infrastructure provider to verify monitoring and identify adjustments that can made to limit the possibility of this occurring again in the future.

9:00am ET - The issue has been resolved. Further analysis of the incident will be posted in this thread today.

8:30am ET - The Wicket team is aware of an ongoing issue where single sign-on may produce an error message when attempting to log in to integrations using Wicket SSO. The Wicket admin panel appears unaffected.

An update will be provided at 9:00am ET.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request



Article is closed for comments.