-
-
Notifications
You must be signed in to change notification settings - Fork 366
Description
Is your feature request related to a problem? Please describe.
When using OAuth2, a sign in window pops up that allows signing into SSO pages. Often, these pages save cookies for the user, so when an additional request is made later, the user is already authenticated and a token gets returned without the user having to login again.
This can be problematic during development, since a common usecase is to switch between users. However, since a cookie is saved on the OAuth/SSO page, it's impossible to logout there and switch to a different user.
Describe the solution you'd like
I think one of the following solutions would work:
- Allow clearing cookies for the embedded sign-in window
- Allow creating different "sessions" for sign-in windows where cookies are not shared
- Add a button that allows opening the sign-in windows without any saved cookies
Describe alternatives you've considered
Using the browser extension allows us to clear the cookies in the browser. That's just a workaround and not a real solution though.