Delinea incident

Platform & SSC : SSO login failures on Delinea Platform (US, EU, UK, CA, AU, SEA and UAE)

Minor Resolved View vendor source →

Delinea experienced a minor incident on October 13, 2026 affecting Platform and Platform and 1 more component, lasting 1h 13m. The incident has been resolved; the full update timeline is below.

Started
Oct 13, 2026, 03:42 PM UTC
Resolved
Oct 13, 2026, 04:56 PM UTC
Duration
1h 13m
Detected by Pingoru
Oct 13, 2026, 03:42 PM UTC

Affected components

PlatformPlatformPlatformPlatformPlatformPlatformSecret Server CloudSecret Server CloudSecret Server CloudSecret Server Cloud

Update timeline

  1. investigating Oct 13, 2026, 03:42 PM UTC

    Between approximately 12:32 UTC and 14:11 UTC on October 13, 2026, some users signing in to the Delinea Platform with SAML single sign-on (SSO) were unable to complete login and received an "Access Denied – Error 15" message after authenticating with their identity provider. Users who were already signed in, and users signing in without SAML SSO, were not affected. The issue was caused by a security rule at a third-party edge network provider that incorrectly blocked SAML login responses. Our engineering team applied a configuration change at 14:11 UTC and SAML SSO logins have been succeeding normally since. If you continue to experience this error, please refresh your browser and try again. We apologize for the inconvenience this has caused and appreciate your patience as we worked to restore normal service. For any questions about this incident, please reach out to our support team at https://support.delinea.com.

  2. identified Oct 13, 2026, 03:44 PM UTC

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

  3. monitoring Oct 13, 2026, 03:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring Oct 13, 2026, 03:50 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Oct 13, 2026, 04:02 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Oct 13, 2026, 04:56 PM UTC

    This incident has been resolved.