Resolved after 6 hours 2 minutes, affecting SysTrack API/UI and SysTrack API/UI and 1 more, on February 3, 2025.
# 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\)
Affected components
Update timeline
- investigating Feb 03, 2025, 12:38 PM UTC
We are currently investigating issues logging in via SAML SSO.
- identified Feb 03, 2025, 03:15 PM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 03, 2025, 03:15 PM UTC
We are continuing to work on a fix for this issue.
- resolved Feb 03, 2025, 06:41 PM UTC
This incident has been resolved.
- 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\)
Your product runs on more than Lakeside Software
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services