This bug has been introduced by upgrading to 2025.5.0, this was all working as expected yesterday on 2025.5.0.
Using authentication in folder settings > OAuth 2 > Client Credentials.
If I make a request in Env1 the token is correctly fetched and applied to my requests.
When I change to Env2, all my requests now fail with 401 Unauthorized
If I delete the token from folder settings > OAuth 2, then a new token is generated and my requests work.
Decoding the token, I can see that the token available after in Env2 immediately after switching from Env1 and making a new request is still using the clientId from Env1.
Please authenticate to join the conversation.
Released
Feedback
Bug
11 months ago

Jack McQuinn
Get notified by email when there are changes.
Released
Feedback
Bug
11 months ago

Jack McQuinn
Get notified by email when there are changes.