Cached OAuth credentials survive account switches on the associated Discord client #2
Description
Issue
Credentials granted to the app through OAuth2 authorization in the Discord client are subsequently cached by the app. This, however, causes problems when a user switches the account in their Discord client, either through the user switcher built into the Discord client itself, or by signing out and subsequently signing in with a different account, as the credentials are only valid for the previous account, and not the one that has been newly signed in.
Potential Resolutions
Either:
- Credential logic is updated to cache multiple credentials and differentiate the credentials between users (via their user ID), and upon a user switch, the authentication step is repeated to authorize the application against the new user. This is more difficult, but is better UX. It may not be possible due to difficulties detecting a user switch. I'll have to dig into this.
- A "sign out" button is added to the settings page. This will immediately invalidate all cached credentials and request fresh OAuth2 credentials for the new user. This would be a lot simpler, but is significantly worse UX. It'll end up being likely what happens if detecting a user switch isn't possible.