Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
1 task done
naolaregaqena opened this issue Apr 2, 2024 · 3 comments
Labels
bug Something isn't working need testing Needs to be tested before merging onto production

Comments

@naolaregaqena
Copy link

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

  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

@naolaregaqena naolaregaqena added bug Something isn't working need testing Needs to be tested before merging onto production labels Apr 2, 2024
@liyasthomas
Copy link
Member

cc: @nivedin @amk-dev

@JunaidOfficialNow
Copy link

cc: @nivedin @amk-dev

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

@liyasthomas
Copy link
Member

@JunaidOfficialNow — Sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working need testing Needs to be tested before merging onto production
Projects
None yet
Development

No branches or pull requests

3 participants