mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3477] [feature]: Allow collection requests to share the authorization method #1174
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#1174
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 @jeliebig on GitHub (Oct 26, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3477
Is there an existing issue for this?
Summary
This feature would allow users to configure the authorization method in the collection itself, so every request in that collection inherits it (including an already obtained token) and doesn't need to be configured again. Users are allowed to override the authentication method for every request if they wish to do so. For authorization methods like OAuth2 the collection is able to obtain and refresh the token manually and/or automatically and allows requests to use it.
Note:
The Postman importer should be able to import the authorization method for collections as well.
Why should this be worked on?
@liyasthomas commented on GitHub (Oct 26, 2023):
We're working on this feature, could you track its progress in #2259?
Possibly a duplicate of #2259, so it's closing.
@jeliebig commented on GitHub (Oct 26, 2023):
I tried multiple keyword searches and somehow still missed that issue, sorry for that!
Thank you for linking me to an existing issue!