You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Open API v3 security schema can be applied to the whole API or to individual operations by adding the security section on the root level or operation level, respectively. https://swagger.io/docs/specification/authentication/
When the security section is applied globally to the whole API, I expect, after importing the swagger definition, that the created collection Authorization property would be set accordingly to the swagger definition and the Authorization property for every request would be set to 'Inherit auth from parent'. However, currently, importing the swagger definition sets the Authorization property for every request instead.
To Reproduce
Steps to reproduce the behavior:
Go to File -> Import to import the attached swagger definition.
A new collection will be created.
Expand the collection
Select the 'status' request and observe that the Authorization property was set to "Bearer Token"
Select the 'healthz' request and observe that the Authorization property was set to "Bearer Token"
Expected behavior
The Authorization property for both 'status' and 'healthz' requests is set to 'Inherit auth from parent' and the collection Authorization property is set to "Bearer Token"
App information (please complete the following information):
Setting a security scheme in OAS should auto-configure a collection to use that type of auth, as well as tell all endpoints to inherit from parent. Importing a OAS spec with hundreds of endpoints is useless when I have to manually go through each of them to point auth to the same scheme.
We just moved from Stoplight to Postman, and found that there are still multiples features of OpenAPI 3 that are not yet supported.
It would be great to be able to know if the problems are at least being worked on. It seems there hasn't been much reaction from the Postman team on a few issues :(
Describe the bug
The Open API v3 security schema can be applied to the whole API or to individual operations by adding the security section on the root level or operation level, respectively. https://swagger.io/docs/specification/authentication/
When the security section is applied globally to the whole API, I expect, after importing the swagger definition, that the created collection Authorization property would be set accordingly to the swagger definition and the Authorization property for every request would be set to 'Inherit auth from parent'. However, currently, importing the swagger definition sets the Authorization property for every request instead.
To Reproduce
Steps to reproduce the behavior:
A new collection will be created.
Expected behavior
The Authorization property for both 'status' and 'healthz' requests is set to 'Inherit auth from parent' and the collection Authorization property is set to "Bearer Token"
App information (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: