Skip to content
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

Bearer Authentication #532

Open
seranotannason opened this issue Jul 15, 2020 · 1 comment
Open

Bearer Authentication #532

seranotannason opened this issue Jul 15, 2020 · 1 comment

Comments

@seranotannason
Copy link

@seranotannason seranotannason commented Jul 15, 2020

In the API spec swagger.json, the authentication scheme is defined as:

"Token": {
      "description": "For accessing the protected API resources, you must have received a a valid JWT token after registering or logging in. This JWT token must then be used for all protected resources by passing it in via the 'Authorization' header.\n\nA JWT token is generated by the API by either registering via /users or logging in via /users/login.\n\nThe following format must be in the 'Authorization' header :\n\n    Token: xxxxxx.yyyyyyy.zzzzzz\n    \n",
      "type": "apiKey",
      "name": "Authorization",
      "in": "header"
    }

Shouldn't it be of "type": "http", "scheme": "bearer", "bearerFormat": "JWT"?

@geromegrignon geromegrignon added this to Triage in V2 Jul 6, 2021
@geromegrignon
Copy link
Contributor

@geromegrignon geromegrignon commented Nov 15, 2021

Right the expected format in securitySchemes: section of the API Documentation should be:

BearerAuth: 
      type: http
      scheme: bearer
      bearerFormat: JWT 

Changes would have to be made in the v2 branch as Token is still used as a solution.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
V2
Triage
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants