Bug description

The following 4.1.1 phenomena did not occur in 4.0.2 It's happening.

・Privileges set to Public (The permissions of the environment in which it occurred are the same, so I think it includes permissions that are not related to the phenomenon.)

can read on Chart can read on Dashboard can list on DynamicPlugin can time range on Api can explore json on Superset can recent activity on Log can read on CssTemplate can samples on Datasource can read on Dataset can explore on Superset can csv on Superset database access on [TEST] can read on Tag

・Dashboard Contents

TAB-1(initial selection state) 2 native filters (A, B All Required)

TAB-2 3 native filters (A, B, C All Required)

※For the native filters A, B, and C, the value for which the target data does not exist Default setting (e.g. 9999)

・Phenomena View Dashboard Without Logging In

1.No input to the native filter Selectable of TAB-1 and TAB-2

2.Enter a native filter in TAB-1, then apply and refresh dashboard view Select TAB-2 → be taken to the login screen

If you add "can write on Dashboard" to Public, the login screen will not appear.

Screenshots/recordings

Description.pdf Added PDF file of description(February 26, 2025)

Superset version

4.1.1

Python version

3.10

Node version

Not applicable

Browser

Chrome

Additional context

No response

Checklist

  • [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
  • [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
  • [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Comment From: qingdao05

What happens if I create a user with the same rights as described and log in? Can I refer to the relevant dashboard without any problem?

If I can see the dashboard correctly, it seems to be strange behavior due to some kind of malfunction.

Comment From: aikawa-ohno

Thank you for your opinion. I was able to view the dashboard correctly when I logged in with the same permissions. (I changed the title because I thought the content was not correct this time.)

Comment From: aikawa-ohno

When I upgraded to 4.1.2, the problem disappeared.