Hi all, We're using SpiceDB with PostgreSQL RLS p...
# spicedb
l
Hi all, We're using SpiceDB with PostgreSQL RLS policies. Our current setup involves querying the LookupResources endpoint from within PostgreSQL RLS policies (using an HTTP extension) to filter records based on the IDs returned by SpiceDB. This ensures that users only see data they are authorized to access. We're trying to figure out the best way to leverage Zed Tokens in this approach. We're currently querying SpiceDB on every request to our database (through RLS policies). 1. What would you recommend in terms of storing these Zed Tokens? Can we simply store a token for each table in our Postgres schema and then anytime that table has a create update or delete update the zed token, or is there a better strategy? 2. Is our current approach of querying LookupResources within PostgreSQL RLS policies fundamentally flawed? Is there a better way to approach this problem altogether? Any insights or recommendations on using Zed Tokens in this context, or alternative approaches, would be greatly appreciated!
6 Views