-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
OAuth 2.0 authentication issues in 9.2.0 version #7508
Comments
your need the version 2022 |
Hi @krthk6000 could you try with the latest version and let me know if this is fixed for you? |
@emman122 it would be great if you could download the latest beta from https://github.com/Kong/insomnia/releases/tag/core%409.3.2 and see if this problem is fixed. If so, we will include it in the next GA in a couple of weeks. |
No
El mié, 24 de jul de 2024, 7:55 a. m., Marco Palladino <
***@***.***> escribió:
… @emman122 <https://github.com/emman122> it would be great if you could
download the latest beta from
https://github.com/Kong/insomnia/releases/tag/core%409.3.2 and see if
this problem is fixed. If so, we will include it in the next GA in a couple
of weeks.
—
Reply to this email directly, view it on GitHub
<#7508 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJNNCEYA7S25P4O2EP4JIOTZN6W6NAVCNFSM6AAAAABI54RXN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBYGAZDMMRUHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Facing the same issue. If it works on a request level - it works all the time. |
Expected Behavior
Should be able to fetch access token or refresh access token with Oath 2.0 authentication.
Actual Behavior
Failed to fetch token url status=0. no description provided
Reproduction Steps
Is there an existing issue for this?
Additional Information
No response
Insomnia Version
9.2.0
What operating system are you using?
Windows
Operating System Version
Windows 11 Enterprise
Installation method
.exe file from website
Last Known Working Insomnia version
NA
The text was updated successfully, but these errors were encountered: