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

Without "can time range on Api", a click on a custom filter redirect to login page #30005

Open
3 tasks
xavier-GitHub76 opened this issue Aug 23, 2024 · 3 comments
Open
3 tasks
Labels
authentication:access-control Rlated to access control

Comments

@xavier-GitHub76
Copy link
Contributor

Bug description

Without "can time range on Api", a click on a custom filter redirect to login page

How to reproduce the bug

Without_.can_time_range_on_Api._a_click_on_a_custom_filter_redirect_to_login_page.mp4

Screenshots/recordings

No response

Superset version

4.0.2

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Copy link

dosubot bot commented Aug 23, 2024

The issue you're encountering is likely due to missing permissions for the "can time range on Api" feature. This permission is required for users to access the time_range method in the API, which is essential for handling custom filters. Without this permission, the system redirects the user to the login page.

To resolve this, ensure that the user has the necessary permissions. The "can time range on Api" permission is available to users with the Admin, Alpha, and Gamma roles, but not to users with the SQL_LAB role [1][2].

You can assign the appropriate role to the user or explicitly grant the "can time range on Api" permission to their current role.

To continue talking to Dosu, mention @dosu.

@Suvendu-UI
Copy link

is this issue resolved ?

@xavier-GitHub76
Copy link
Contributor Author

In the absence of permission ("can time range on Api" or others), it would be preferable to have an error message rather than a redirection to the login page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
authentication:access-control Rlated to access control
Projects
None yet
Development

No branches or pull requests

2 participants