We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using a top level defined apiKey as query parameter, the apiKey is not recognized in requests.
$ curl localhost:8000/v1/check?apiKey=testtest
{"message":"query parameter 'apiKey' required","errors":[{"path":"/v1/check","message":"query parameter 'apiKey' required"}]}
Reson is that we are looking in the headers, not in the query param ;)
else if (scheme.in === 'query') { if (!req.headers[scheme.name]) { throw Error(`query parameter '${scheme.name}' required`); } }
Will send a PR
The text was updated successfully, but these errors were encountered:
fix apiKey as query parameters not picked up by security middleware Fix
c52e571
cdimascio#92
Send PR: #93
Sorry, something went wrong.
@comino. Thanks for the PR. I'll get this merged in and published. Thank you!
Successfully merging a pull request may close this issue.
When using a top level defined apiKey as query parameter, the apiKey is not recognized in requests.
Reson is that we are looking in the headers, not in the query param ;)
Will send a PR
The text was updated successfully, but these errors were encountered: