MapColonies / MapColonies/geocoding
express-openapi-validator ignores securitySchemes token query param (MAPCO-5197)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- express, openapi, typescript
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100