Implementing RLS in ThoughtSpot with Existing DBT Logic
Hi team,
I’m reaching out to see if anyone has experience or insights on this.
Currently, we have Row-Level Security (RLS) implemented in DBT, and we're using OAuth authentication to authenticate users to Snowflake. However, due to a recent requirement, we now need to shift the RLS logic to ThoughtSpot, mirroring what’s already built in DBT and change the connection to service account.
I’m looking for guidance or best practices on how to:
. Implement RLS within ThoughtSpot in a reliable and scalable way.
. Reuse or replicate the existing logic from DBT to ensure consistency.
. Handle OAuth-based user authentication or equivalent identity propagation in this new setup.
If anyone has worked on a similar migration or has implemented RLS directly in ThoughtSpot, your suggestions or pointers would be greatly appreciated.
Thanks in advance!
I’m reaching out to see if anyone has experience or insights on this.
Currently, we have Row-Level Security (RLS) implemented in DBT, and we're using OAuth authentication to authenticate users to Snowflake. However, due to a recent requirement, we now need to shift the RLS logic to ThoughtSpot, mirroring what’s already built in DBT and change the connection to service account.
I’m looking for guidance or best practices on how to:
. Implement RLS within ThoughtSpot in a reliable and scalable way.
. Reuse or replicate the existing logic from DBT to ensure consistency.
. Handle OAuth-based user authentication or equivalent identity propagation in this new setup.
If anyone has worked on a similar migration or has implemented RLS directly in ThoughtSpot, your suggestions or pointers would be greatly appreciated.
Thanks in advance!
