GitHub user Yash-alternativepath added a comment to the discussion: Seeking Some Help On DataSource Security / RLS
@dosu I don’t think the issue is simply about which schema the query is executed in. The real problem is that Superset tries to match the table to apply RLS using both the schema and table name. So when a user runs a query without specifying the schema (e.g., SELECT * FROM table_x), Superset interprets it as coming from None.table_x, whereas the RLS rule is defined for public.table_x. Since the schema doesn’t match, RLS doesn’t get applied. So how adjust_engine_params this will work ?? or any other workaround? GitHub link: https://github.com/apache/superset/discussions/33308#discussioncomment-13008319 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
