michael-s-molina commented on PR #25352:
URL: https://github.com/apache/superset/pull/25352#issuecomment-1729351955

   > You will notice that I did not include them within the RowLevelSecurity 
class because they were not yet present in Apache Superset version 2.1.0. I 
needed this functionality in the version I am using in a specific production 
environment.
   
   In scenarios like this, the best approach is to contribute to the master 
version, to ensure the contribution will be available in subsequent releases, 
and wait for a minor version of your current release that includes the new 
feature. An alternative is to just implement this feature locally for your 
deployment but you'll need to support it when upgrading.
   
   > the endpoints already present allow you to extract information from the 
RLS table but do not help you extract the RLS for that specific username or 
role, generally the Client does not know which role the user is associated with.
   
   > If for that specific user or role there are several RLS filters of the 
Regular / Base type and with different group key values, it is necessary for 
the Client to carry out all the logical aggregation operations (AND, OR) to 
generate the list of dictionaries used later in the endpoint body 
/api/v1/security/guest_token/.
   
   I'm pretty sure we can resolve these use cases by a combination of filters 
(`q` request parameter) and token augmentation if the required information is 
not there already. I'll ping some folks that know more about the embedded 
feature and can help you. @rusackas @lilykuang @betodealmeida @yousoph 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to