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

SqlLab preview permissions error #20511

Closed
2 of 3 tasks
mporracindie opened this issue Jun 27, 2022 · 1 comment
Closed
2 of 3 tasks

SqlLab preview permissions error #20511

mporracindie opened this issue Jun 27, 2022 · 1 comment
Labels
#bug Bug report

Comments

@mporracindie
Copy link
Contributor

mporracindie commented Jun 27, 2022

Permissions error on sql lab preview even tho the user has schema access.

How to reproduce the bug

  1. Create a rol X with schema access on Y
  2. Give a user the following roles: X, Gamma and SqlLab
  3. The user can now query the schema but the preview fails with:
You need access to the following tables: `%60___%60.%60___%60`,
            `all_database_access` or `all_datasource_access` permission

Screenshots

Screen Shot 2022-06-27 at 17 16 13

Screen Shot 2022-06-27 at 17 16 38

Environment

(please complete the following information):

  • browser type and version: Chrome Version 102.0.5005.115 (Official Build) (arm64)
  • superset version: 1.4.1
  • python version: 3.8.12
  • any feature flags active: No

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are 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.
@mporracindie mporracindie added the #bug Bug report label Jun 27, 2022
@rusackas
Copy link
Member

rusackas commented Feb 7, 2024

Since we're now on 3.1, on the verge of 4.0, we're not supporting 2.x or prior versions actively. If anyone is experiencing this issue in current versions, please file a new issue with updated context and repro steps. Thank you for understanding :)

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

No branches or pull requests

2 participants