-
Notifications
You must be signed in to change notification settings - Fork 221
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
Multiple values for authentication #2023
Comments
Having the same issue here! |
Stoplight elements currently incorrectly interprets the OpenAPI specification regarding the security requirement objects.
Specifically a security like this: security:
- apiKey: []
accessToken: [] must be interpreted as security:
- apiKey: []
- accessToken: [] means Currently both types are simply flattened into a single array of choices. |
same issue #1794 |
Having the same issue! |
At the end, we are moving away to another product with proper support. |
Multiple Authentication parameters
As a web user, I'd like to do "Try It!" with authorization token and user ID, but it's not currently possible (I've checked even code of this project, and seems like this is not possibility, yet).
We are currently moving from using Postman to Stoplight. While moving, we got an issue, where we want to send
Authorization: Bearer token
and headerX-ACCOUNT-ID: 123
, as one user can have multiple accounts in our system.Luckily, this is part of OpenAPI spec (multiple parameters by no leading dash between security parameters). However, this is not working in elements.
The ID is used as part of the authentication, so it's not really something we'd like to mark as parameter for each and every endpoint we have.
Example for this in OpenAPI
The text was updated successfully, but these errors were encountered: