Created
September 4, 2018 17:32
-
-
Save Maniacal/02211e71b248e3a32613a119c96361b4 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'm trying to report a bug but the "Submit new issue" button is greyed out on both the swagger-ui and swagger-editor projects. I pasted the content below (sorry about the markdown). Not sure what else I should do. | |
Bug report contents: | |
- OS: Linux Mint | |
- Browser: Chrome | |
- Version: 68 | |
- Method of installation: docker container | |
- Swagger-Editor version: [e.g. 3.10.0] Not sure, "latest" as of 2 weeks ago | |
- Swagger/OpenAPI version: OpenAPI 3.0.1 | |
### Content & configuration | |
This bug is in both Swagger Editor and Swagger UI but only reporting it here. | |
Example Swagger/OpenAPI definition: | |
```yaml | |
openapi: 3.0.1 | |
info: | |
version: 1.0.0 | |
title: Stores Endpoint | |
description: 'Products, Departments, Brands, and Categories API endpoints.' | |
servers: | |
- url: https://example.com/v1 | |
security: | |
- Oauth2: | |
- read | |
- write | |
paths: | |
/stores: | |
get: | |
description: Gets all `stores` data | |
responses: | |
'200': | |
description: Successful response | |
content: | |
application/json: | |
schema: | |
$ref: '#/components/schemas/StoreListReturn' | |
components: | |
securitySchemes: | |
Oauth2: | |
type: oauth2 | |
flows: | |
clientCredentials: | |
tokenUrl: https://example.com/accesstoken | |
refreshUrl: https://example.com/refresh_accesstoken | |
scopes: | |
read: Grant read access | |
write: Grant write access | |
``` | |
Swagger-Editor configuration options: | |
### Describe the bug you're encountering | |
The Authorization header being generated uses the word "BearerToken" instead of "Bearer" as specified in the OAuth 2.0 RFC (https://tools.ietf.org/html/rfc6749). I can see this tracing the calls from the Editor and the UI and it is also visible looking at the curl command that is generated | |
``` | |
curl -X GET "https://example.com/v1/stores" -H "accept: application/json" -H "Authorization: BearerToken pdOxgV0ZuZyuPRyM99GvCpgk1eGu" | |
``` | |
### Expected behavior | |
I expect the token to be sent with "Bearer" instead of "BearerToken" per the RFC. | |
`Authorization: Bearer <token>` | |
### Screenshots | |
### Additional context or thoughts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment