search

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.5k stars 1.95k forks source link

OAuth 2.0 authentication issues in 9.2.0 version #7508

Open krthk6000 opened 3 months ago

krthk6000 commented 3 months ago

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

  1. create a GET request
  2. Set the AUTH type to Oath 2.0 and grant type to client credentials
  3. set access token url, client ID and client secret

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

emman122 commented 3 months ago

your need the version 2022

gatzjames commented 2 months ago

Hi @krthk6000 could you try with the latest version and let me know if this is fixed for you?

subnetmarco commented 2 months ago

@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.

emman122 commented 1 month ago

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 https://github.com/Kong/insomnia/issues/7508#issuecomment-2248026248, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJNNCEYA7S25P4O2EP4JIOTZN6W6NAVCNFSM6AAAAABI54RXN6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBYGAZDMMRUHA . You are receiving this because you were mentioned.Message ID: @.***>

pjastrzabek commented 3 weeks ago

Facing the same issue. When I try to set up Oauth 2.0 on some parent level - it never works. When I apply the same settings on a request level - sometimes it works, sometimes it does not with the mentioned error.

If it works on a request level - it works all the time. If it does not work on some other request - it's also not working all the time. It may be working for request A, while not working for request B at the same time (all settings are the same for both)