Resolved after 6 hours 5 minutes, affecting RyderShip-Core, on September 3, 2019.
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.
Affected components
Update timeline
- investigating Sep 03, 2019, 07:21 PM UTC
We are currently investigating an issue with the 2.0 API related to refreshing tokens.
- 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
- 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.
Your product runs on more than Whiplash
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services