Kong / insomnia

The open-source, cross-platform API client for GraphQL, REST, WebSockets, SSE and gRPC. With Cloud, Local and Git storage.
https://insomnia.rest
Apache License 2.0
34.56k stars 1.96k forks source link

Functionality "Refresh Token" in tab "OAuth 2" does not get authentication token #5820

Open leomarcamargo opened 1 year ago

leomarcamargo commented 1 year ago

Expected Behavior

The authentication token should be generated normally, as it was generated in versions prior to version 2021.5.3 regardless of the application environment.

Actual Behavior

Since version 2021.5.3 I cannot use the Refresh Token functionality in a local environment because whenever I click on the Refresh Token button I get the error Failed to fetch token url=https://localhost:5001/connect/token status=0 no description provided. However, if I point it to any environment other than localhost, the functionality presents no problem.

This functionality, until version 2021.5.3, works without any problems, but since then I can no longer use it with the new versions. Also, when I click on Response Timeline, no information is shown on the screen. See the images below:

https://prnt.sc/wMfyHsCQpS88 https://prnt.sc/Xu9dRoy_qmRi https://prnt.sc/gyOAUv8ZIiLP

Reproduction Steps

  1. In the OAuth 2 tab , enter the necessary data of grant type, access token url, client id and client secret;
  2. Click on the Refresh Token button.

Is there an existing issue for this?

Additional Information

No response

Insomnia Version

2022.7.5

What operating system are you using?

Windows

Operating System Version

Windows 10

Installation method

Download from Insomnia

Last Known Working Insomnia version

2021.5.3

Edodums commented 1 year ago

Me too , the OAuth works once and only with one of my APIs ( everytime I reinstall everything is different ) but all the other ones in my workspace can't do anything. I've to manually reinstall everytime the 2021 Insomnia.Core-2022.6.0.dmg because it's the last version where I can at least manually insert the token in the three last sections ( and even If I uncheck the auto update, it auto updates itself )

mkstephenson commented 1 year ago

I am getting this as well. Although in this case I fetch the token from our auth server and run the request against a server running on localhost, I still get the "status=0 no description provided" response with no further details on what went wrong.