Why access to Superset dashboard with created user role not working in my case?

[do-you-zorya]

Hello!
I trying make access to dashboard to every employee of company. For every employee I create user with role "salary_role".

I created new user with new role and add this to dashboard.
After that I add this permissions for "salary_role":

1. can read on SavedQuery;
2. can read on Chart;
3. can read on Dashboard;
4. can filter on Superset;
5. menu access on Dashboards
6. datasource access on [Clickhouse Connect].[] for every dataset, used in dashboard including filters.

After sing in with new user I can see and open my dashboard.
But I see error for filters:

Cannot load filter
Error: HTTPDriver for http://clickhouse:8123 received ClickHouse error code 516 Code: 516. DB::Exception: ******k: Authentication failed: password is incorrect, or there is no user with such name. (AUTHENTICATION_FAILED) (version 24.1.5.6 (official build)) 

But sometimes I can use filters or use one of filters (for example I can use filter "A", but get error for filter "B" even they using the same dataset).

That I've done wrong and how to configure access by user_role to dashboard?

P. S. I'm using superset-image apache/superset:4.0.0 with Docker.

[dosubot[bot]]

The issue you're experiencing seems to be related to authentication problems with the ClickHouse connection, as indicated by the error message. Here are a few steps to troubleshoot and resolve the issue:

1. Verify ClickHouse Credentials: Ensure that the credentials (username and password) used in the ClickHouse connection string are correct. The error message suggests that there might be an issue with the authentication details provided.

2. Check Role Permissions: You've already set up the necessary permissions for the "salary_role". Double-check that the datasource access permission is correctly configured for all datasets used in the dashboard, including those used in filters.

3. Caching Issues: Intermittent access issues could be related to caching. Superset's caching mechanism for filters might cause such problems if there are connectivity issues with the caching backend or misconfigurations. Ensure that your cache configuration is correct and that the caching service (e.g., Redis) is running smoothly ^[1].

4. Superset Configuration: Make sure that your Superset configuration is correctly set up to handle ClickHouse connections. This includes ensuring that the ClickHouse driver is properly installed and configured in your Docker setup ^[2].

5. Test Connection: Use the "Test Connection" feature in Superset's database connection settings to verify that the connection to ClickHouse is stable and correctly configured.

By addressing these areas, you should be able to resolve the authentication and filter access issues you're encountering.

To continue talking to Dosu, mention @dosu.