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
Crash using OAuth2 authorization #5926
Labels
Comments
zroger
added
B-bug
Bug: general classification
S-unverified
Status: Unverified by maintainer
labels
Apr 27, 2023
I get the similar error with Implicit Authentication with OKTA:
|
According to the electron docs the url load failed because of the error code was probably caused by the redirecting before the page is fully loaded. -3 Abort Error "An operation was aborted (due to user action)." should probably be ignored. |
Event is actually generated from here when url redirects. |
jackkav
added a commit
to jackkav/insomnia
that referenced
this issue
Nov 24, 2023
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Expected Behavior
Insomnia opens a browser window to allow the OAuth2 authorization code workflow to proceed.
Actual Behavior
The browser window opens, then Insomnia immediately crashes.
Reproduction Steps
I can reproduce this with my company's Okta server, which uses the Okta IWA Agent. The authorization URL does some stuff in javascript which results in an immediate redirect, at which point there is an
ERR_ABORTED
raised from the child browser window. This feels similar to electron/electron#17526.Is there an existing issue for this?
Additional Information
Logs from the crash:
I was able to get authorization to work by simply ignoring the
ERR_ABORTED
raised fromchild.loadURL
inauthorizeUserInWindow
like this, but I'm not familiar enough with the project to know if this would have unintended consequences.Insomnia Version
2023.2.0
What operating system are you using?
macOS
Operating System Version
13.3.1
Installation method
homebrew
Last Known Working Insomnia version
No response
The text was updated successfully, but these errors were encountered: