Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
OAuth 2.0 Authorization Window does not respect "Validate certificates" setting
See original GitHub issueDescribe the bug When fetching a new “authorization code” token with help from the OAuth 2.0 auth helper, if the “Authorization URL” uses a self-signed certificate, the Authorization Window appears, but is blank. This is regardless of the “Validate certificates” setting in the preferences window.
To Reproduce Steps to reproduce the behavior:
- Set the “Validate Certificates” setting in the preferences window to “false” (unchecked):
- In an “OAuth 2.0” mode auth tab, enter valid settings including:
- The “grant type” field with a value of “Authorization Code”
- The “authorization URL” field pointing to an HTTPS URL which does not use a valid HTTPS certificate (such as
localhostor127.0.0.1)
- Click on ‘Fetch Tokens’
- Note the blank window appearing and no network traffic
- Note the error in the DevTools console, despite the “Validate certificates” setting from earlier:
Uncaught (in promise) Error: ERR_CERT_AUTHORITY_INVALID (-202) loading 'https://127.0.0.1:5001/connect/authorize?response_type=code&client_id=insomnia&redirect_uri=https%3A%2F%2Ffake.url%2Foidc-callback&scope=openid%20profile%20email%20otherscopes&state=820813df-8ca6-4fd3-83c5-45fd3f1a5f7a'
Expected behavior Assuming “Validate certificates” is set to false (unchecked), the Authorization Window should correctly send a request to the Authorization URL server and display the HTML response so the user can authenticate.
Desktop:
- OS: macOS 10.15.7 (this might be important as this could be a macOS specific issue)
- Installation Method: Manual Install (
.dmgdownload from website) - App Version: Insomnia Core 2020.4.1
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This does actually appear to be working for me now. I had an issue with the certificate which, when fixed, seemed to make the login /validation work as expected.