-
Notifications
You must be signed in to change notification settings - Fork 258
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
Error using AUTHENTICATION_WHITELIST
to disable auth in OpenAPI schema
#923
Comments
A workaround I just found out to be working is passing an authentication backend that is not currently in use in the project, and the security schema is returned empty / the button is not shown. |
Good point. I just tried to come up with a value that was supposed to satisfy your requirement. This was not an official feature, but I think is worth adding. |
I agree it would be nice to have. I think just a |
new default allowAll is None. [] is denyAll
@tfranzel, I tested it and passing an empty list hides the Authorization button on the GUI. May I suggest that this be documented, also? |
@niccolomineo awesome! I think this is kinda documented here: 0dfa1dc#diff-9748fb54622c822b7d9a2e29ff074cd8ed22d17b8de898f1ea6d69afcef82c75R160 I would refrain from documenting implementation details of SwaggerUI though. That would be a bottomless pit and I won't even try to 😆 |
Hi @tfranzel, as you suggested here, I tried to pass:
in
SPECTACULAR_SETTINGS
to suppress the security scheme, but I am getting:I am using drf 3.14.
The text was updated successfully, but these errors were encountered: