Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Restrict SQL Lab access to datasource #18014

Closed
victorarbuesmallada opened this issue Jan 12, 2022 · 1 comment
Closed

Restrict SQL Lab access to datasource #18014

victorarbuesmallada opened this issue Jan 12, 2022 · 1 comment
Labels
question & help wanted Use Github discussions instead

Comments

@victorarbuesmallada
Copy link
Contributor

Hi all,

We are trying to figure out ways of restricting the datasources we can perform SQL Lab queries and it seems that the most granular thing we can achieve is restrict access per schema, which grants accesss to ALL the datasources under that schema, something that we don't want.

Is there any way we could have a restriction based only on datasource at all?

@geido
Copy link
Member

geido commented Jan 12, 2022

Hello @Painyjames I had a look at several combinations of permissions and I could not reach your desired state. You might get better chances of having an answer in the Superset Slack. I'll be happy to get you in touch with someone who might help over there.

@geido geido added the question & help wanted Use Github discussions instead label Jan 12, 2022
@apache apache locked and limited conversation to collaborators Feb 2, 2022
@geido geido converted this issue into discussion #18369 Feb 2, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
question & help wanted Use Github discussions instead
Projects
None yet
Development

No branches or pull requests

2 participants