starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #3956] [bug]: Cannot specify both `apiKey` on `Authorization` tab and jwt bearer token on the header. #1386

New issue

Closed

opened 2026-03-16 20:06:34 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 20:06:34 +03:00

Owner

Originally created by @naolaregaqena on GitHub (Apr 2, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3956

Originally assigned to: @anwarulislam on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When i specify an apiKey in Authorization section of a collection, folder or request and also specify JWT token on the header as Authorization: Bearer ... as so. the api key is removed in the request header. i expect for both of them to be passed on the header. both have different keys header to not assume they getting overridden. this is occurring on hoppscotch aio version 2024.3.0.

Steps to reproduce

Go to the either self hosted or cloud version of hoppscotch.
Create a collection. can be either personal workspace or team workspace.
Add an api key on Authorization section of the collection properties.
Optionally create a folder and set the authorization property to inherit.
Create a request and similarly set its authorization property to inherit.
Navigate to header section of the request, the api key should be visible. as soon as an Authorization header is set the api key header disappears, and it is not passed on the header of the request.

Environment

Production

Version

Self-hosted

Originally created by @naolaregaqena on GitHub (Apr 2, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3956 Originally assigned to: @anwarulislam on GitHub. ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When i specify an `apiKey` in `Authorization` section of a collection, folder or request and also specify JWT token on the header as `Authorization: Bearer ...` as so. the api key is removed in the request header. i expect for both of them to be passed on the header. both have different keys header to not assume they getting overridden. this is occurring on `hoppscotch aio version 2024.3.0`. ### Steps to reproduce 1. Go to the either self hosted or cloud version of hoppscotch. 2. Create a collection. can be either personal workspace or team workspace. 3. Add an api key on Authorization section of the collection properties. 4. Optionally create a folder and set the authorization property to `inherit`. 5. Create a request and similarly set its authorization property to `inherit`. 6. Navigate to header section of the request, the api key should be visible. as soon as an `Authorization` header is set the api key header disappears, and it is not passed on the header of the request. ### Environment Production ### Version Self-hosted

kerem

2026-03-16 20:06:34 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 20:06:50 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 2, 2024):

cc: @nivedin @amk-dev

@liyasthomas commented on GitHub (Apr 2, 2024): cc: @nivedin @amk-dev

kerem commented

2026-03-16 20:06:55 +03:00

Author

Owner

@JunaidMancheri commented on GitHub (Apr 2, 2024):

cc: @nivedin @amk-dev

may i take look into this.. and solve this?

@JunaidMancheri commented on GitHub (Apr 2, 2024): > cc: @nivedin @amk-dev may i take look into this.. and solve this?

kerem commented

2026-03-16 20:07:00 +03:00

Author

Owner

@liyasthomas commented on GitHub (Apr 2, 2024):

@JunaidOfficialNow — Sure.

@liyasthomas commented on GitHub (Apr 2, 2024): @JunaidOfficialNow — Sure.

kerem commented

2026-03-16 20:07:06 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Apr 3, 2025):

Hi, closing this issue as it's resolved in the latest release. Please feel free to let us know if you have any feedback.

@jamesgeorge007 commented on GitHub (Apr 3, 2025): Hi, closing this issue as it's resolved in the latest release. Please feel free to let us know if you have any feedback.

kerem referenced this issue

2026-03-17 00:54:08 +03:00

[PR #1386] [MERGED] Update fr-FR.json #3272

kerem referenced this issue

2026-03-17 00:57:26 +03:00

[PR #1470] [MERGED] i18n #3331

kerem referenced this issue

2026-03-17 00:59:53 +03:00

[PR #1527] [MERGED] i18n translations #3380