express-openapi-validator ignores securitySchemes token query param (MAPCO-5197)

Open
#44 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
express, openapi, typescript
Domain
api, authentication, backend

Research direction

Start by inspecting how express-openapi-validator processes OpenAPI securitySchemes and how this repository defines routes. Reproduce the token query-parameter case, then confirm that authentication works without manually adding token to every route.

Written by the indexing model from the issue text.

Description

bug

In the next version 0.1.4, users will be able to authenticate via token query parameter.
For some reason, express-openapi-validator ignores the token definition in securitySchemes and I had to manually set token as a query param in every route. We need to check if theres another and more elegant solution.

Dominant language
TypeScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MapColonies/geocoding

All issues in MapColonies/geocoding

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.