Skip to content
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

ChartFilter filters on datasource instead of chart #23969

Closed
jingapore opened this issue May 8, 2023 · 2 comments
Closed

ChartFilter filters on datasource instead of chart #23969

jingapore opened this issue May 8, 2023 · 2 comments

Comments

@jingapore
Copy link

jingapore commented May 8, 2023

ChartFilter here should filter on chart access, not datasource access.

This has downstream implications:

The correct thing is for chart access to be separated from datasource access. ChartFilter needs to be amended.

@jingapore jingapore changed the title ChartFilter filters on datasource instead of chart ChartFilter filters on datasource instead of chart #bug May 9, 2023
@jingapore jingapore changed the title ChartFilter filters on datasource instead of chart #bug ChartFilter filters on datasource instead of chart May 9, 2023
@SaviorXTanren
Copy link

To add to this, the same sort of logic is present in the Datasets list. When a user visits the Datasets list page, it shows all Datasets of the Datasources that the user has access to. So users will be able to see Datasets that they do not have permission and it will fail for them when they attempt to navigate to any of them.

Similarly, visiting a Dataset that you don't have access to will expose the names of the columns in the dataset, even though you don't have access to query on it.

There should be a trickle down check done on these sorts of pages. For example, if you go to Charts list, it should check first to see what Datasources you have access to, and then individually check the Charts in those Datasources to ensure you have access to each one before it is shown in the list. Same sort of idea for Datasets, Dashboards, etc.

@rusackas
Copy link
Member

This is likely fixed by now, and is pretty out of date if not. If people are still encountering this in current versions (3.x) please open a new Issue or a PR to address the problem, or add a reproducible example here so we can re-open this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants