Repository navigation
security(#237): revoke excess anon grants and drop duplicate RLS policies - #249
Merged
Merged
Conversation
… RLS policies Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Part 1 — revoke excess anon privileges across all 14 public tables:
TRUNCATE— bypasses RLS at the PostgreSQL level; PostgREST never exposes it but the privilege was thereTRIGGER/REFERENCES— never used by PostgREST; pointless for the anon rolePart 2 — drop legacy
{public}ALL policies that are exact duplicates of later{authenticated}replacements:"Trenere ser egne økter"onsessions"Tilgang via session"onsession_exercises"Tilgang via session_exercise"onmuscle_activationsThe
{public}copies never granted anon access in practice (every USING clause checksauth.uid(), which is null for unauthenticated requests), but they added evaluation overhead and policy-list noise. The{authenticated}replacements with identical USING clauses remain."Same-gym users can read sessions"({public}SELECT) is intentionally kept — it has no{authenticated}duplicate and provides co-instructor cross-visibility.Migration applied to production via Supabase MCP and verified with two spot-check queries.
Test plan
anonhas no TRUNCATE/TRIGGER/REFERENCES on any public table (verified live){public}ALL policies dropped;{authenticated}replacements intact (verified live)"Same-gym users can read sessions"still present🤖 Generated with Claude Code