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
there is a very strange behavior of drf-spectacular when defining Authentication classes from simple-jwt when you declare JWTAuthentication as default_authentication_class swagger UI authorize button works correctly but when you declare JWTTokenUserAuthentication as default_authentication_class swagger UI authorize button disappears and can not set Bearer token.
Steps to reproduce:
first, create a Django project with rest framework and drf-spectacular and simple jwt installed and configured with documentation guidance.
now go to /api/schema/swagger-ui/ everything works fine
then change authentication classes to:
and refresh boom!! there is no authorize button at all!!! it looks like if you subclass JWTAuthentication class it goes wrong.
I did not know where to post this issue but so posted it on both, can anybody help me to fix drf-spectacular with this authentication class? @tfranzel
The text was updated successfully, but these errors were encountered:
there is a very strange behavior of drf-spectacular when defining Authentication classes from simple-jwt when you declare JWTAuthentication as default_authentication_class swagger UI authorize button works correctly but when you declare JWTTokenUserAuthentication as default_authentication_class swagger UI authorize button disappears and can not set Bearer token.
Steps to reproduce:
first, create a Django project with rest framework and drf-spectacular and simple jwt installed and configured with documentation guidance.
now go to /api/schema/swagger-ui/ everything works fine
then change authentication classes to:
and refresh boom!! there is no authorize button at all!!! it looks like if you subclass JWTAuthentication class it goes wrong.
I did not know where to post this issue but so posted it on both, can anybody help me to fix drf-spectacular with this authentication class?
@tfranzel
The text was updated successfully, but these errors were encountered: