-
Notifications
You must be signed in to change notification settings - Fork 24
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
API Key Auth not correctly being assigned to header #104
Comments
I notice in the test (
|
hi @millerdrew Thanks for providing the details for what seems to be a bug. |
@thim81 Sure. Here's a simplified export: API Example.postman_collection.zip The major difference from what's in the test appears to be this line is missing: "in": "header" instead there's only key, value, and type thanks for the response appreciate your help! let me know if anything else would be useful |
hi @millerdrew Is this issue still happening? |
hi @millerdrew I tried to reproduce your case, but I'm not able to fully understand your issue. This is the converted result:
|
We have the following logic in lib\auth\apikey.js
I have my Postman collection auth defined like this:
A snippet from the json output from my exported collection:
It appears to be incorrectly using config.options instead of config.headers so my auth to fail when using the generated k6s output. If I manually change that part the auth works.
Perhaps something has changed in the output from Postman that's causing the line
if (params.get('in') === 'header') {
to not work as expected?Here is my Postman version:
The text was updated successfully, but these errors were encountered: