-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
feat(dashboard_rbac): dashboard_view access enforcement #12875
feat(dashboard_rbac): dashboard_view access enforcement #12875
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of code style suggestions. Mostly non-blockers.
The HTML error renderer could be a large refactoring effort that'd worth a discussion thread or separate PR.
Codecov Report
@@ Coverage Diff @@
## master #12875 +/- ##
==========================================
- Coverage 66.93% 59.25% -7.68%
==========================================
Files 1022 966 -56
Lines 50186 45927 -4259
Branches 5204 4444 -760
==========================================
- Hits 33591 27216 -6375
- Misses 16455 18711 +2256
+ Partials 140 0 -140
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM. Thanks for all the updates. Just one more comment that's non-blocking, too.
Let's leave this PR open for a couple of more hours just in case others have thoughts.
Unfortunately, this feature breaks my dataset-based access. I can either use dashboard level OR dataset level. I've ran a db upgrade after setting the FF as well. What went wrong? (I am on 1.4.1) |
SUMMARY
resolves #10408
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TEST PLAN
go to the dashboard(http://127.0.0.01/superset/dashboard//) to which you have no access (no role nor dataset access)
dashboard should not be visible and should get forbidden 403
ADDITIONAL INFORMATION