You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an alert or a report is sent by schedule, its data depends on the 'THUMBNAIL_SELENIUM_USER' value in config.
so we can't apply RLS(Row Level Security) for a specific purpose.
Proposed Change
If an operator sets the 'THUMBNAIL_SELENIUM_USER' to None in superset_config.py, the user will be set as the first owner of its alert(report) schedule for sending an alert(or a report) by default.
New or Changed Public Interfaces
No - As far as I know...
New dependencies
N/A
Migration Plan and Compatibility
N/A
Rejected Alternatives
Improve 'Notification Method'(in a schedule setting) can support like 'Login as' feature. so just one schedule setting covers sending multiple reports with different RLS. In this case, we also have to think about the security problem.(which user can be set as a 'login as' and is it valid.)
The text was updated successfully, but these errors were encountered:
Motivation
When an alert or a report is sent by schedule, its data depends on the 'THUMBNAIL_SELENIUM_USER' value in config.
so we can't apply RLS(Row Level Security) for a specific purpose.
Proposed Change
If an operator sets the 'THUMBNAIL_SELENIUM_USER' to None in superset_config.py, the user will be set as the first owner of its alert(report) schedule for sending an alert(or a report) by default.
New or Changed Public Interfaces
No - As far as I know...
New dependencies
N/A
Migration Plan and Compatibility
N/A
Rejected Alternatives
Improve 'Notification Method'(in a schedule setting) can support like 'Login as' feature. so just one schedule setting covers sending multiple reports with different RLS. In this case, we also have to think about the security problem.(which user can be set as a 'login as' and is it valid.)
The text was updated successfully, but these errors were encountered: