Skip to content
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.

Sign up for GitHub

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

Jump to bottom

AWS CLI v2 sso login browser redirects are broken in the latest version of Chrome #5539

Closed
2 tasks done
nfplatzke opened this issue Sep 14, 2020 · 4 comments
Closed
2 tasks done

AWS CLI v2 sso login browser redirects are broken in the latest version of Chrome #5539

nfplatzke opened this issue Sep 14, 2020 · 4 comments
Labels
bug This issue is a bug. v2

Comments

@nfplatzke
Copy link

Confirm by changing [ ] to [x] below to ensure that it's a bug:

Describe the bug
The command "aws sso login" fails and hangs during the redirects when the latest version of chrome is set as the default browser. I have verified this issue with the latest version of AWS CLIv2 (aws-cli/2.0.48 Python/3.7.4 Darwin/17.7.0 exe/x86_64). During the failed redirect chain the token is consumed so you can not even follow the manual steps that are displayed in the output.

The bug can be worked around by setting a different default browser. I am not sure if this is something that can be worked around in the CLI tool, but it is browser specific. However I wanted to open this bug because it could be avoided if #5533 was implemented.

SDK version number
aws-cli/2.0.48 Python/3.7.4 Darwin/17.7.0 exe/x86_64

Platform/OS/Hardware/Device
OSX

To Reproduce (observed behavior)
Run "aws sso login" with the latest version of chrome. The redirect chain stops and hangs at a blank screen. The token is consumed so you can't even manually finish the process.

Expected behavior
Normal login.

Logs/output
Get full traceback and error logs by adding --debug to the command.

Additional context
Add any other context about the problem here.
@nfplatzke nfplatzke added the needs-triage This issue or PR still needs to be triaged. label Sep 14, 2020
@kdaily kdaily added the v2 label Sep 14, 2020
@kdaily
Copy link
Member

kdaily commented Sep 14, 2020

Hi @nfplatzke, can you confirm the version of Google Chrome you are using? I see the most recent version as 85.0.4183.102. Thanks!

@kdaily kdaily added bug This issue is a bug. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. and removed needs-triage This issue or PR still needs to be triaged. labels Sep 14, 2020
@nfplatzke
Copy link
Author

@kdaily yes, that is correct.

Version 85.0.4183.102 (Official Build) (64-bit)

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label Sep 14, 2020
@nfplatzke
Copy link
Author

This issue seems to have been resolved. No changes were made to my cli install or chrome so I am thinking something changed in the way the SSO handoff is being done. In either case, this can be closed. But I think #5533 would still be helpful

@kdaily
Copy link
Member

kdaily commented Sep 17, 2020

Hi @nfplatzke, glad to hear. I see you commented on #5533, so thanks for adding your feedback there.

@kdaily kdaily closed this as completed Sep 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug This issue is a bug. v2
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kdaily @nfplatzke