mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #358] Feature request: OAuth header support/integration #132
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#132
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 @jamiehowarth0 on GitHub (Nov 27, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/358
Is your feature request related to a problem? Please describe.
A number of APIs and services are protected using OAuth these days, and it would be great to integrate an OAuth-specific header builder (similar to Postman) to enable easy testing of OAuth-protected resources.
Describe the solution you'd like
A header "builder" to construct an OAuth Authorization header.
Describe alternatives you've considered
None so far.
Additional context

This is a list of the authentication schemes that Postman supports - for a free tool, OAuth in particular would be very useful.
@AndrewBastin commented on GitHub (Nov 27, 2019):
Hi there,
Thanks for opening the issue. OAuth is something really important to many workloads and is indeed a high priority thing to be implemented.
@liyasthomas @jamesgeorge007 @NBTX @athul @izerozlu
Anyone willing to pick this issue up ? I am a bit in a handful with getting native wrapper going.
@liyasthomas commented on GitHub (Nov 27, 2019):
@benjaminhowarth1 isn't this how OAuth JWT token is sent in a request?
Authorization: Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxthis is already implemented in Authorization section as Bearer token.
@AndrewBastin commented on GitHub (Nov 27, 2019):
OAuth does use some standard URL parameters though....
We can look into those ?
@liyasthomas commented on GitHub (Nov 27, 2019):
I can do that.