Skip to content

Incident detail

SSO-OIDC Authentication Issue

Resolved incidentMinor1 affected service

Timeline window

to

Get alerted the next time JumpCloud breaks

Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Timeline

Incident updates

Every update on the official status source, oldest to newest, exactly as it appeared there.

  1. Investigating

    We are currently investigating an issue with the authentication on SSO OIDC applications. We have already identified the cause and will provide an update within one hour.

  2. Identified

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

  3. Monitoring

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

  4. Resolved

    This incident has been resolved.

  5. Resolved

    ![](https://jumpcloud.com/wp-content/themes/jumpcloud/assets/images/jumpcloud-press-kit/logos/02-jc-richblack-tm.png)

    ‌

    Date: Nov 13, 2025

    Date of Incident: Nov 6, 2025

    Description: RCA for SSO/OIDC Service Degradation

    ‌

    Summary:

    On November 6, 2025, starting at approximately 12:00 UTC, customers experienced failures to launch any application relying on JumpCloud's OIDC-based Single Sign-On (SSO), lasting for roughly one hour.

    ‌

    Root Cause:

    The outage was caused by a combination of two errors during a scheduled compliance procedure:

    1. Faulty Password Generation: Our automated system for rotating database passwords created a new credential that contained unsafe special characters.

    2. Missing Special Character Logic: The entrypoint script for our core SSO service was missing logic to handle these special characters before using the password to construct a database connection string.

    When the SSO service attempted to restart and use the newly rotated password, the presence of the unsafe characters caused the connection string to be misinterpreted as invalid, leading to a parsing failure and service degradation.

    This issue stemmed from a latent configuration bug that was masked by prior rotation processes. Previously, database passwords were rotated manually using an older system (`random_password` IAC resource) which was explicitly configured to only generate alphanumeric characters. These characters are inherently safe in a URL context, so the underlying bug in the SSO service's connection logic was never exposed.  When the credential management was successfully migrated to the new, more robust rotation process, the new function began generating highly complex passwords, including special characters, for the first time. This immediately triggered the latent parsing flaw in the SSO service’s entrypoint script.

    ‌

    Corrective Actions / Risk Mitigation:

    1. Hardening code logic - All services that construct database connection strings will be audited and updated to explicitly encode the password component eliminating character misinterpretation.

    2. Enhanced rotation alerting -  New monitoring and alerting dashboards are in place to track the health and success schedule of all automated credential rotation jobs, providing an immediate alert if a rotation creates an invalid credential.

    3. Update password generation logic - The automated credential rotation function has been updated to explicitly generate passwords that are safe, avoiding complex, reserved characters.

Keep exploring

More from JumpCloud

Neighboring incidents on JumpCloud's timeline and the rest of their record on OutageDeck.