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
Authorization Code Flow for Single Page Applications: Cleanup Popup Flows and Window Nav #1236
Authorization Code Flow for Single Page Applications: Cleanup Popup Flows and Window Nav #1236
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, I still think we could do with less inline comments overall, but I appreciate the focus and smaller size on this PR. Much easier to review and understand!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to use addEventListener
and removeEventListener
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving. Please close Jason's comments and merge it.
…cleanupPopup-flows Authorization Code Flow for Single Page Applications: Cleanup Popup Flows and Window Nav
This PR adds cleanup for different popup related errors, as well as window navigation actions such as redirect and refresh. This does not affect token acquisition, but does force users to be aware that handleRedirectCallback() should not be used with the popup APIs, as it will cause the window to handle the response in the popup, rather than the main window.
This should fix the issue raised in #1231.