-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
The DASHBOARD_RBAC feature flag doesn't seem to work as intended, even with the example dataset #31938
Comments
Hey @Mayeu! 👋 There are a few similar discussions related to issues with the
Regarding your specific issue, the error message indicates that the user lacks the necessary Additionally, ensure that the To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Allowing myself to poke direct members of this repository (@villebro, @amitmiran137, @geido), because this bot answer is not useful. I know all those tickets, I have read them, and one of them is just a poor user fighting against that bot. Please deactivate issue responses from that bot. Auto-labelling is fine, but on most issues I saw here the bot seems to just add noise and confuse users. |
From the error it seems the gamma user does not have access to the data source the dashboard is deriving it's data from? Have you give the gamma user permission to access the data source as well? or only assigned the dashboard to the gamma role? |
Correct, that's what
As this issue demonstrates, enabling DASHBOARD_RBAC and granting a role access to a dashboard does not bypass dataset level checks, so that's a bug. |
I always CC @dpgaspar when RBAC bugs come up 🤞 |
Bug description
Hello 👋,
Activating the
DASHBOARD_RBAC
feature flag doesn't work as intended, we can't share access to our dashboard that way on our production instance, and it doesn't work locally either with the example dataset.63843c568255d5f1302815ed7614e93d7febadae
)DASHBOARD_RBAC
feature flag indocker/pythonpath_dev/superset_config.py
docker compose -f docker-compose-non-dev.yml up --build
Exception in the log:
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.11
Node version
16
Browser
Chrome
Additional context
I have read through various tickets that seems to also encounter this bug, but no solution describes there solved the issue , and most seems to only be for older version of Superset (and most where riddle with misleading AI slop).
So I decided to open this ticket to show that even with the example data this feature flag doesn't seem to work. Or maybe there are missing steps in the documentation for activating this?
Checklist
The text was updated successfully, but these errors were encountered: