-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Swagger API page is empty #24616
Comments
@kgabryje I checked and it seems CSP is blocking the Swagger inline scripts. |
Thank you for reporting this issue. A fix was done on FAB to support nonce's also, currently release on 4.3.4rc1. Hope to publish a final release soon |
FAB 4.3.4 is out and considered a new minor version on Superset |
Hi. I still get an empty page for /swagger/v1 when using the latest-dev image. I built from that image 6 days ago. Any help would be appreciated. |
As of 3.0.0, I also get an empty page. |
Disabling Talisman fixed this issue for me. I am not sure how the two should be related. Logging in as the administrator from the UI should give you access to Swagger's UI. |
Talisman sets CSP that is currently preventing a swagger css and a js code block from running |
I still have an empty page with v3.0.0. Should I still need to disable Talisman for this? |
After deploying superset in docker, the swagger page(/swagger/v1) displayed nothing except the superset menu header.
The configuration FAB_API_SWAGGER_UI has been set to True in config.py.
Expected results
All superset APIs should be listed.
Actual results
An empty page.
How to reproduce the bug
Go to https://host:port/swagger/v1
An empty page was displayed
The text was updated successfully, but these errors were encountered: