One Identity Starling incident

PAM Essentials Issue with web-based RDP sessions

Major Resolved View vendor source →

One Identity Starling experienced a major incident on November 20, 2025 affecting PAM Essentials and PAM Essentials, lasting 12d 17h. The incident has been resolved; the full update timeline is below.

Started
Nov 20, 2025, 09:28 PM UTC
Resolved
Dec 03, 2025, 02:32 PM UTC
Duration
12d 17h
Detected by Pingoru
Nov 20, 2025, 09:28 PM UTC

Affected components

PAM EssentialsPAM Essentials

Update timeline

  1. investigating Nov 20, 2025, 09:28 PM UTC

    We are investigating an issue impacting web-based RDP sessions when using Chromium-based browsers in PAM Essentials. SSH Sessions are unaffected. Workarounds: using non-Chromium browsers such as Firefox or accessing services through native clients have proven effective.

  2. investigating Nov 20, 2025, 11:32 PM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 21, 2025, 03:08 AM UTC

    We are continuing to investigate this issue.

  4. investigating Nov 21, 2025, 04:19 AM UTC

    We are continuing to investigate this issue.

  5. investigating Nov 21, 2025, 10:54 AM UTC

    We're investigating a possible issue related to session launch using the Chromium based browsers where the session fails unexpectedly. The native client is unaffected. Access via Firefox browser also works fine.

  6. investigating Nov 21, 2025, 01:02 PM UTC

    We're investigating a possible issue related to session launch using the Chromium based browsers where the session fails unexpectedly. The native client is unaffected. Access via Firefox browser also works fine.

  7. investigating Nov 21, 2025, 02:17 PM UTC

    We're investigating a possible issue related to session launch using the Chromium based browsers where the session fails unexpectedly. The native client is unaffected. Access via Firefox browser also works fine.

  8. investigating Nov 21, 2025, 03:31 PM UTC

    We're investigating a possible issue related to session launch using the Chromium based browsers where the session fails unexpectedly. The native client is unaffected. Access via Firefox browser also works fine.

  9. investigating Nov 21, 2025, 04:42 PM UTC

    We're investigating a possible issue related to session launch using the Chromium based browsers where the session fails unexpectedly. The native client and Firefox are not impacted. We will continue to work on this issue over the weekend. The next update is scheduled for Monday morning. If any relevant change to the situation happens, we will update the statuspage.

  10. investigating Nov 24, 2025, 10:01 AM UTC

    We're investigating a possible issue related to session launch using the Chromium based browsers where the session fails unexpectedly. The native client is unaffected. Access via Firefox browser also works fine.

  11. investigating Nov 24, 2025, 03:40 PM UTC

    We're investigating a possible issue related to session launch using the Chromium based browsers where the session fails unexpectedly. The native client and Firefox are not impacted. We will continue to work on this issue. The next update is scheduled for Tuesday morning. If any relevant change to the situation happens, we will update the statuspage.

  12. investigating Nov 25, 2025, 10:11 AM UTC

    We're investigating a possible issue related to session launch using the Chromium based browsers where the session fails unexpectedly. The native client is unaffected. Access via Firefox browser also works fine.

  13. investigating Nov 26, 2025, 09:58 AM UTC

    We're investigating a possible issue related to session launch using the Chromium based browsers where the session fails unexpectedly. The native client is unaffected. Access via Firefox browser also works fine.

  14. identified Nov 28, 2025, 11:36 AM UTC

    We have identified the root cause of the issue and a fix is being implemented.

  15. identified Dec 01, 2025, 09:15 AM UTC

    We have identified the root cause of the issue and a fix is being implemented.

  16. identified Dec 02, 2025, 06:23 PM UTC

    We have identified the root cause of the issue and a fix is being implemented.

  17. monitoring Dec 03, 2025, 09:29 AM UTC

    We deployed the fix to production. Currently monitoring it.

  18. resolved Dec 03, 2025, 02:32 PM UTC

    This incident is resolved