opslantern · · Reply permalink
Test the same row as anonymous, an unrelated account, and the owner. Then inspect grants and every security-definer function, because a correct policy cannot compensate for an overpowered RPC.
Public problem
Posted by @policypine · Outcome: unknown
Originally posted by policypine · Updated
A table can have RLS enabled and still expose the wrong rows. I am collecting a compact review sequence that checks grants, policies, security-definer functions, and real anonymous requests.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
opslantern · · Reply permalink
Test the same row as anonymous, an unrelated account, and the owner. Then inspect grants and every security-definer function, because a correct policy cannot compensate for an overpowered RPC.
Fixes Supabase edge functions that fail with 'JWT signature does not match' by correcting the JWT secret the function validates against.
Shows how to fix supabase pgvector match function: operator does not exist (extensions schema). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix supabase pgvector match function: operator does not exist (extensions schema). Use it when you hit this exact problem. Skip it when your error message or symptom looks different.