How to grant access for anonymous / no login users to a dashboard.

[digimen-ch]

I have a dashboard with 2 charts and two data sources. As described here: https://superset.apache.org/docs/security/#public I added

PUBLIC_ROLE_LIKE = "Gamma"

to my superset_config.py and added permission for the two data sources to role Gamma. No effect. So I was digging around and found this

AUTH_ROLE_PUBLIC = "Public"

But also this doesn't work. It seems the documentation is not complete, ChatGPT not helpful at all and after wasting half a day for this simple task I'm quite annoyed.

I run superset Version: 4.0.2 on debian 12, nginx, gunicorn. Many thanks for your help.

[digimen-ch]

Great. A bot. If I want to talk to a bot I go talk to a bot. I got all this kind of answers already several times.

I set

AUTH_ROLE_PUBLIC = "Public"
PUBLIC_ROLE_LIKE = 'Gamma'

I set the permissions to the public role

The gamma role have the necessary permissions:

I did restart several times. Other settings, TALISMAN for example, work properly.

[vasileiosvyzas]

@digimen-ch did you find a solution after? I am facing the same problem.

[digimen-ch]

Unfortunately not. I just want to test the tool and don't have much time to waste to find a solution. Let me know if you find one.

[vasileiosvyzas]

I tried to follow the suggestions from this issue here: #7763. I think what worked for me was the following two commands. To be honest I made so many changes before I run the commands so I am not sure if this did the trick.
superset update db
superset init

[aikawa-ohno]

The following URL is in Japanese but may be helpful.

https://qiita.com/azarashin/items/f3adddf0f989e4f4399a

Excerpts below

According to mistercrunch:

did you run superset init ? Public should then be like Gamma, to which you can start adding tables / databases

Look at this, actually.
superset init -> edit superset_config.py -> run superset run,

started to suspect that the procedure was actually wrong,

Edit superset_config.py -> superset init -> superset run

[sfirke]

Try creating a role called Public with the permissions listed here: #29709 (comment)
Then enable the DASHBOARD_RBAC feature flag (noted in a different part of the docs, sorry) and assign the Public role to the dashboard you want to make public.

I see PUBLIC_ROLE_LIKE is still used in the codebase, so that's a bummer it didn't work. I wonder if / how those docs on the Security Configurations page need to be updated.