Lakeside Software incident

SAML SSO Issues against Regions

Minor Resolved View vendor source →

Lakeside Software experienced a minor incident on February 3, 2025 affecting SysTrack API/UI and SysTrack API/UI and 1 more component, lasting 6h 2m. The incident has been resolved; the full update timeline is below.

Started
Feb 03, 2025, 12:38 PM UTC
Resolved
Feb 03, 2025, 06:41 PM UTC
Duration
6h 2m
Detected by Pingoru
Feb 03, 2025, 12:38 PM UTC

Affected components

SysTrack API/UISysTrack API/UISysTrack API/UISysTrack API/UISysTrack API/UISysTrack API/UISysTrack API/UI

Update timeline

  1. investigating Feb 03, 2025, 12:38 PM UTC

    We are currently investigating issues logging in via SAML SSO.

  2. identified Feb 03, 2025, 03:15 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Feb 03, 2025, 03:15 PM UTC

    We are continuing to work on a fix for this issue.

  4. resolved Feb 03, 2025, 06:41 PM UTC

    This incident has been resolved.

  5. postmortem Feb 06, 2025, 01:34 PM UTC

    # What was the issue? Less than 4% of our customers had login issues when using SAML SSO following the 11.2 upgrade. # What was the root cause? During our standard SDLC, we updated a software package to its latest version. This update introduced stricter controls on the IDP Entity Setting, preventing login if customers didn't adhere to the recommended Entity setting. # What is the Prevention Strategy? Lakeside 1. worked directly with customers to update their SAML SSO Settings \(Completed\) 2. will preform additional testing for library updates \(On Going\)