-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
How to deal with authentication #118
Comments
Currently, spectree will validate the data and generate the OpenAPI document. If the validation failed, it will return 422 with details. It doesn't support special Auth parameters #56 and status code 401 or 403. If you want to use this library with authentication and authorization, you can define the schema for headers and do the auth by yourself. I know this is not perfect. Welcome PR. |
The ability to specify whether the endpoints are protected by authorization (particularly per endpoint or/and in general on app level) and if so, to specify what kind of authorization is uses - a very needed feature. Please, add it. |
Yes. Very true. Subscribed as well. |
Will merge it to another branch and fix the lint today. |
@kemingy Thanks a lot, and congrats for this awesome project! |
How authentication and authorization should be used with spectree?
The text was updated successfully, but these errors were encountered: