rusackas commented on issue #42239: URL: https://github.com/apache/superset/issues/42239#issuecomment-5025019172
Thanks @ketansharma78. That exact toast is a useful clue. When Superset itself denies a dashboard save, the UI shows "You do not have permission to edit this dashboard" instead. The ": Forbidden" variant only appears when the 403 response body isn't Superset's JSON, which usually means something in front of Superset (reverse proxy, WAF, SSO gateway) rejected the PUT before it reached the app. Large dashboard save payloads are a classic WAF false positive. Could you open the browser devtools Network tab, retry the save, and share the response body and headers of the failing `PUT /api/v1/dashboard/<id>`? Also which Superset version you're on and what sits in front of it. I pinned that toast mapping with a test in #42250 so it stays a reliable signal. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
