question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Slice and Dashboard lists don't respect `database` and `schema`-related perms

See original GitHub issue

Make sure these boxes are checked before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if any
  • I have reproduced the issue with at least the latest released version of superset
  • I have checked the issue tracker for the same issue and I haven’t found one similar

Superset version

Latest

Expected results

When database access on [db].(id:#) is granted to a role, it should have the effect of also granting datasource access on all data sources in the DB. Per https://superset.incubator.apache.org/security.html - “Database: Granting access to a database allows for the user to access all data sources within that database”

Actual results

It does not grant data source access. In order to grant data source access, the datasource_access permission has to be granted for each table in the DB.

Steps to reproduce

  1. Fresh install the current version of Superset
  2. Create new role, “Main”, add database_access on [main].(id:1)
  3. Create new user with “Gamma” and “Main” roles
  4. Log in as new user

Notes

This is similar to #3085 but that issue was closed, and this issue is reproducible from a fresh install. The tables are accessible if datasource access is granted for each table, but in my DB, there are hundreds of tables and I’d prefer to not have to manually add each one as a permission. I’d be happy to investigate too if someone pointed me in the right direction.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

3reactions
rumbincommented, Nov 7, 2019

@mistercrunch: It seems that this issue is still present, at least in Superset 0.34.1. I also do not see why this issue had been closed, as there is no link to any PR or any stale-bot interaction.

Would you mind reopening it?

0reactions
grbinhocommented, May 20, 2020

I’m seeing the same behaviour with the latest image from https://hub.docker.com/r/preset/superset/

Read more comments on GitHub >

github_iconTop Results From Across the Web

[permissions] database_access does not grant access to ...
From the documentation "Granting access to a database allows for ... Dashboard lists don't respect database and schema -related perms #6077.
Read more >
Loading metadata - IBM
After a data server connection is created, you need to load the metadata from the database schemas or catalogs. Only schemas where metadata...
Read more >
Frequently Asked Questions - Apache Superset
To clarify, the database backend is an OLTP database used by Superset to store its internal information like your list of users, slices...
Read more >
Schema Organization - Civis Analytics
Database Permissions : This approach allows you to limit the permissions that users have to production database schemas so that they don't even ......
Read more >
All other San Diego fixes - Product Documentation | ServiceNow
ServiceNow Performance dashboard release notes ... Info message on related list can overlap other text/buttons (background of info message ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found