Changing the environment doesn't invalidate my authentication token

I have created environments for switching between different users using oAuth2. The clientId, tokenUrl or authorizationUrl stays the same, but the username and password are different.

This has been reported before

https://feedback.yaak.app/en/p/token-not-refreshing-when-switching-environments, but since the keys are clientId, tokenUrl and authorizationUrl, this doesn’t cause the token to switch when only the user credentials are different.

Wouldn’t it be best to use a full hash of the configuration of the authentication as a key? Right now, I always have to click “Delete Token” when I change my environments.

Please authenticate to join the conversation.

Upvoters
Status

Needs Triage

Board

Feedback

Tags

Bug

Date

6 months ago

Author

Michaël Arnauts

Subscribe to post

Get notified by email when there are changes.