Whiplash incident

API Token Authorization

Major Resolved View vendor source →

Whiplash experienced a major incident on September 3, 2019 affecting RyderShip-Core, lasting 6h 5m. The incident has been resolved; the full update timeline is below.

Started
Sep 03, 2019, 07:21 PM UTC
Resolved
Sep 04, 2019, 01:26 AM UTC
Duration
6h 5m
Detected by Pingoru
Sep 03, 2019, 07:21 PM UTC

Affected components

RyderShip-Core

Update timeline

  1. investigating Sep 03, 2019, 07:21 PM UTC

    We are currently investigating an issue with the 2.0 API related to refreshing tokens.

  2. investigating Sep 04, 2019, 01:25 AM UTC

    v2 API authentication has been resolved. A recent Oauth upgrade now requires refresh requests to include a `client_id` and `client_secret` in the refresh request: https://docs.getwhiplash.com/pages/authentication-for-the-v2-api#refresh-tokens

  3. resolved Sep 04, 2019, 01:26 AM UTC

    V2 refresh tokens now need the client_id and client_secret included in the Post body. See https://docs.getwhiplash.com/pages/authentication-for-the-v2-api#refresh-tokens for more information.