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
I've been talking to the maintainer of OpenAPI.NET on Github, and he says that the way I should override an operation to indicate "anonymous" is to get OpenAPI.NET to render a new security section with an empty JSON object in; for example:
In addition, this has been brought to the attention of the swagger-ui project, and they've agreed with this behaviour and modified swagger-ui to display no padlock for such a security override, indicating "no authorization".
At the moment, when I generate a collection from an API definition in Postman, such an override still results in an "inherit from parent" security setting for that endpoint. It should be generated with "no auth".
The text was updated successfully, but these errors were encountered:
I've been talking to the maintainer of OpenAPI.NET on Github, and he says that the way I should override an operation to indicate "anonymous" is to get OpenAPI.NET to render a new security section with an empty JSON object in; for example:
In addition, this has been brought to the attention of the
swagger-ui
project, and they've agreed with this behaviour and modified swagger-ui to display no padlock for such a security override, indicating "no authorization".At the moment, when I generate a collection from an API definition in Postman, such an override still results in an "inherit from parent" security setting for that endpoint. It should be generated with "no auth".
The text was updated successfully, but these errors were encountered: