Prismatic incident

OAuth2 tokens with custom headers fail to refresh

Critical Resolved View vendor source →

Prismatic experienced a critical incident on April 26, 2023 affecting OAuth 2.0 Refresh, lasting 1h 3m. The incident has been resolved; the full update timeline is below.

Started
Apr 26, 2023, 06:08 PM UTC
Resolved
Apr 26, 2023, 07:11 PM UTC
Duration
1h 3m
Detected by Pingoru
Apr 26, 2023, 06:08 PM UTC

Affected components

OAuth 2.0 Refresh

Update timeline

  1. identified Apr 26, 2023, 06:08 PM UTC

    A regression in how custom headers are handled with OAuth2 tokens has caused issues with integrations that use them. We have identified the issue and are working to deploy a fix.

  2. identified Apr 26, 2023, 06:43 PM UTC

    A fix is being deployed to all affected regions.

  3. monitoring Apr 26, 2023, 07:03 PM UTC

    A fix has been deployed to all regions and OAuth2 tokens are refreshing normally.

  4. monitoring Apr 26, 2023, 07:06 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Apr 26, 2023, 07:11 PM UTC

    This incident has been resolved.