mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 09:16:03 +03:00
[GH-ISSUE #5356] [bug]: JWT Authorization can not be generated #2047
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#2047
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 @rocascent on GitHub (Aug 28, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5356
Originally assigned to: @anwarulislam, @MOUNIAT-1002 on GitHub.
Is there an existing issue for this?
Platform
Desktop App
Browser
Other (specify in additional info)
Operating System
Windows
Bug Description
I fill in the JWT auth form with secret and payloads, but it don't generate a header/param when requesting.
This problem doesn't appear in the Web App.
Deployment Type
Hoppscotch Cloud
Version
2025.8.0
@shiv7shukla commented on GitHub (Sep 7, 2025):
Hi I'm Shiv a second year college student and I would like to contribute to this repo by fixing this bug can you tell me more about this bug or share a screenshot regarding the issue.
@rocascent commented on GitHub (Sep 8, 2025):
@MOUNIAT-1002 commented on GitHub (Sep 15, 2025):
Hello,
I would like to work on this issue, may someone assign it to me please.
@anwarulislam commented on GitHub (Oct 6, 2025):
Hello @Gn3po4g and @MOUNIAT-1002,
If anyone wishes to contribute to this issue, please inform me. We plan to address this in the upcoming release; therefore, those who decide to take this reply on this comment. Otherwise, we will handle it on our end. The next release is scheduled for the end of this month.
@MOUNIAT-1002 commented on GitHub (Oct 6, 2025):
hello @anwarulislam ,
i want to contribute to this issue.
@anwarulislam commented on GitHub (Oct 6, 2025):
@MOUNIAT-1002 you can start working on the issue.