You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem here is that we replay a fixture for that expired access token, but the new data calls need a valid token.
A couple ways to remedy this:
The easiest way is that the normalizer should not delete any properties (e.g. sig, or possibly a date) that would replay old tokens for new requests.
The harder way is to re-record all previously replayed requests that share that same identity. (However, what will this mean for previously-recorded responses that depend on those headers?)
The text was updated successfully, but these errors were encountered:
Here's the scenario:
401
.The problem here is that we replay a fixture for that expired access token, but the new data calls need a valid token.
A couple ways to remedy this:
normalizer
should notdelete
any properties (e.g.sig
, or possibly a date) that would replay old tokens for new requests.The text was updated successfully, but these errors were encountered: