-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Windows] Cannot logout and login into another account #34
Comments
Hi @tmathern , I am not sure whether this is an issue with the CLI IMS Plugin or with the IMS web app. |
See #32 |
Removing all cookies fixes the issue, indeed. |
Thanks for confirming @tmathern ! While as a CLI user I expect to be logged in automatically if I am logged in from the browser, I still feel it weird to be logged out in the browser if I log out from my CLI. WDYT? |
I agree that the user should not be automatically logged out in the browser by default. However, it looks like it's not clear (currently) how a user can log out in the current flow without having to manually type in a different URL (experience cloud for instance). Perhaps we should add a logout functionality to the CLI log in UI. |
Logout link in the terminal? How would this flow look like |
Nope, in the web UI that pops-up to login and then to confirm that the user has successfully logged in. |
Yes ^ actually -- let's close this topic and do a separate one for UI improvements on this page. I'm connected with our design team to discuss further! |
Expected Behaviour
After I logout, I want to be able to login again but with another account.
Actual Behaviour
After logout, on the second login, in Chrome, I don't have a chance to switch account because it goes too fast. Therefore, I'm logged in again, but with the wrong account.
Reproduce Scenario (including but not limited to)
Pre-requisite: Working on Windows, with a Chrome browser opening the login page.
Steps to Reproduce
aio auth login
aio auth logout
Platform and Version
Windows 10, Node 14
Sample Code that illustrates the problem
Logs taken while reproducing problem
What happens on subsequent logins: The "you're logged in" page appears nearly immediately.
The text was updated successfully, but these errors were encountered: