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
Swagger-UI version: latest, or as hosted on editor.swagger.io
Swagger/OpenAPI version: OpenAPI 3.0
Example Swagger/OpenAPI definition:
## This can be previewed in https://editor.swagger.io/openapi: "3.0.0"info:
title: Foo APIversion: "0.1.0"description: A test apiservers:
- url: 'https://foo.com/v1/'components:
securitySchemes:
Token: # TODO this isn't sending in swagger-ui??type: httpdescription: Bearer Tokenscheme: Bearersecurity:
- Token: [] # Require token for all requests (unless otherwise specified)paths:
"/myEndpoint":
get:
summary: Authenticated Endpointresponses:
"200":
description: OKcontent:
application/json:
schema:
type: object
Describe the bug you're encountering
No tokens are not being sent in the authorization header. The UI allows me to set the token value but does not include the token when I make a request. The curl code also does not include the token.
To reproduce...
Load the above yaml into swagger ui. Click on the padlock and enter a token. Click 'try it' and then execute a request.
Expected behavior
The executed request and curl should contain the token.
Additional context or thoughts
The padlock appears but it is not being included in requests. I have tried hosting my own swagger-ui and had the same results.
IIRC it was working a few days/weeks ago.
API Key auth still works as expected.
The text was updated successfully, but these errors were encountered:
Q&A (please complete the following information)
Example Swagger/OpenAPI definition:
Describe the bug you're encountering
No tokens are not being sent in the authorization header. The UI allows me to set the token value but does not include the token when I make a request. The curl code also does not include the token.
To reproduce...
Load the above yaml into swagger ui. Click on the padlock and enter a token. Click 'try it' and then execute a request.
Expected behavior
The executed request and curl should contain the token.
Additional context or thoughts
The padlock appears but it is not being included in requests. I have tried hosting my own swagger-ui and had the same results.
IIRC it was working a few days/weeks ago.
API Key auth still works as expected.
The text was updated successfully, but these errors were encountered: