mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4866] [bug]: OAuth 2.0 Authorization on collection stopped working: "AUTH_TOKEN_REQUEST_INVALID_RESPONSE" #1831
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1831
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kamilzki on GitHub (Mar 10, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4866
Originally assigned to: @CuriousCorrelation on GitHub.
Is there an existing issue for this?
Current behavior
After the recent problem with a browser extension (https://github.com/hoppscotch/hoppscotch/issues/4837), the OAuth 2.0 Authorization on collection stopped working.
After clicking "Generate token", I am always getting two errors:
I see no requests are made in the network tab.
The same configuration without browser extensions, by using browser option, works properly and I can see a successful token request in the network too.
Steps to reproduce
Environment
Production
Version
Local
@jamesgeorge007 commented on GitHub (Mar 11, 2025):
Hi, we have a PR with the fix scheduled for the next patch release.
@kamilzki commented on GitHub (Mar 13, 2025):
@jamesgeorge007, tested today with a new release, but unfortunately, the problem still exists
@kamilzki commented on GitHub (Mar 13, 2025):
@jamesgeorge007 sorry! The problem is not resolved -it was a misclick. Please reopen it!
@jamesgeorge007 commented on GitHub (Mar 13, 2025):
Thanks for confirming; we'll be investigating.
@Bastetoi commented on GitHub (Mar 13, 2025):
same issue here just a "fail to fetch token" meanwhile on postman or curl or ... it works with the same credentials/ authentification url
@kamilzki commented on GitHub (Mar 19, 2025):
@jamesgeorge007 The recent fix has successfully resolved the issue. Thanks you so much! 🥳