0Pricing
Supabase Backend as a Service · レッスン

RLSのテストとデバッグ

RLSポリシーが期待どおりに動作することを確認するための効果的なテスト戦略と、アクセスに関する問題のデバッグ方法を学びます。

「RLSのテストとデバッグ」はCoddyKit上の無料Supabase Backend as a Serviceレッスンです。 これはレッスン2/3です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。 これはSupabase Backend as a Service学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Supabase Backend as a Serviceコースには全3レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Why Test RLS Policies?

Row-Level Security (RLS) is powerful, but tricky. It controls who sees and modifies data directly at the database level. A small mistake can expose sensitive information or block legitimate users.

  • Security Assurance: Confirm sensitive data is protected.
  • Functionality: Ensure users can access what they need.
  • Prevent Bugs: Catch unintended access issues early.

Testing RLS is crucial for a secure and functional application.

Two Main Testing Approaches

You can test your RLS policies using two primary methods:

  • SQL Editor (Database Level): Directly interact with your database using SQL, impersonating different users. This is great for isolated testing.
  • Client-Side (Application Level): Test through your application's frontend or backend code, making authenticated API requests. This validates the entire flow.

Both methods offer unique insights into how your RLS policies behave.

Method 1: SQL Editor with SET ROLE

The most direct way to test RLS is by using the Supabase SQL Editor to impersonate a user. PostgreSQL allows you to temporarily assume the permissions of another role (user) using the SET ROLE command.

This lets you run queries as if you were that specific user, observing exactly what data they can see or modify according to your RLS policies.

SET ROLE Demo: Impersonating a User

First, enable RLS on your table. Then, create a policy. Here's how to test it in the SQL Editor. We'll use a dummy user ID for demonstration.

Note: Replace 'auth.jwt()' with your actual JWT payload if you're testing with a real user's token, or use a specific auth.uid() if you have a known user ID.

-- Assume a user with ID 'a1b2c3d4-e5f6-7890-1234-567890abcdef'
SET SESSION AUTHORIZATION 'postgres';

-- Temporarily set the auth.uid() function to return a specific ID
-- In a real scenario, this would be set by the JWT from the client
SELECT set_config('auth.request.jwt.claim.sub', 'a1b2c3d4-e5f6-7890-1234-567890abcdef', TRUE);

-- Now, run a query on a table with RLS enabled
-- For example, if you have a 'posts' table with an 'author_id' column
SELECT * FROM posts;

-- Reset session authorization
RESET SESSION AUTHORIZATION;

-- Clear the custom auth.uid() setting
SELECT set_config('auth.request.jwt.claim.sub', '', TRUE);

Verifying Access with SELECT

After setting the role or mocking the auth.uid(), you can run simple SELECT, INSERT, UPDATE, or DELETE statements to see their effect. If your RLS policy is working, you should only see (or be able to affect) the rows that the impersonated user is allowed to access.

If you see too much, or too little, your policy might need adjustment.

Method 2: Client-Side Testing

Testing RLS through your application code is crucial because it simulates real-world usage. You'll make authenticated requests using the Supabase client library (e.g., JavaScript, Python).

When a user signs in, the client library automatically includes their JWT in API requests. Supabase then uses this JWT to determine the auth.uid() and apply RLS policies accordingly.

Client-Side Demo: Authenticated Fetch

This conceptual JavaScript snippet shows how a logged-in user's session is used to fetch data. The RLS policies on the posts table will automatically filter the results based on the authenticated user.

No specific SET ROLE is needed here; it's handled by the Supabase client and backend.

import { createClient } from '@supabase/supabase-js'

const supabaseUrl = 'YOUR_SUPABASE_URL'
const supabaseAnonKey = 'YOUR_SUPABASE_ANON_KEY'

const supabase = createClient(supabaseUrl, supabaseAnonKey)

async function fetchUserPosts() {
  // Assume user is already signed in
  const { data: { user } } = await supabase.auth.getUser()

  if (user) {
    const { data, error } = await supabase
      .from('posts')
      .select('*')

    if (error) {
      console.error('Error fetching posts:', error.message)
    } else {
      console.log('User posts:', data)
    }
  } else {
    console.log('No user signed in.')
  }
}

fetchUserPosts()

Debugging RLS: EXPLAIN ANALYZE

When RLS isn't behaving as expected, EXPLAIN ANALYZE is your best friend. This SQL command shows you the execution plan of a query, including how RLS policies are applied.

Look for the "Filter" step in the plan. This indicates where your RLS policy conditions are being evaluated. It helps confirm if your policy is even being considered, and if its conditions are efficient.

EXPLAIN ANALYZE Demo

Run this in the SQL Editor (after setting the user role/ID as before) to see how RLS affects the query plan. The output will detail the query execution steps.

Examine the output for lines related to your RLS policy, often appearing as Filter: (auth.uid() = posts.user_id) or similar.

SET SESSION AUTHORIZATION 'postgres';
SELECT set_config('auth.request.jwt.claim.sub', 'a1b2c3d4-e5f6-7890-1234-567890abcdef', TRUE);

EXPLAIN ANALYZE SELECT * FROM posts WHERE id = 1;

RESET SESSION AUTHORIZATION;
SELECT set_config('auth.request.jwt.claim.sub', '', TRUE);

Common RLS Pitfalls

Debugging often involves checking for common mistakes:

  • RLS Not Enabled: Did you run ALTER TABLE your_table ENABLE ROW LEVEL SECURITY;?
  • Missing Policy: No policy means no access (unless default is permissive).
  • Incorrect USING/WITH CHECK: Conditions might not match your intent. USING for reads/updates/deletes, WITH CHECK for inserts/updates.
  • Policy Order: Multiple policies are OR'd together for access.
  • Superuser Bypass: Remember, postgres user bypasses RLS.

Test Your RLS Knowledge

You've learned about testing and debugging RLS. Let's see if you can identify the best way to verify an RLS policy's behavior for a specific user within the Supabase SQL Editor.

Recap: Testing & Debugging RLS

In this lesson, you learned how to effectively test and debug your Row-Level Security policies. We covered:

  • The importance of testing RLS for security and functionality.
  • Using the SQL Editor with SET ROLE and set_config to impersonate users.
  • Testing RLS through client-side authenticated requests.
  • Leveraging EXPLAIN ANALYZE to understand RLS policy application.
  • Identifying and resolving common RLS pitfalls.

Thorough testing ensures your data remains secure and accessible as intended!

よくある質問

「RLSのテストとデバッグ」レッスンは無料ですか？

はい。「RLSのテストとデバッグ」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Supabase Backend as a Serviceコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Supabase Backend as a Serviceコースには全3レッスンが含まれています。

「RLSのテストとデバッグ」で何を学びますか？

RLSポリシーが期待どおりに動作することを確認するための効果的なテスト戦略と、アクセスに関する問題のデバッグ方法を学びます。 ブラウザで直接実行するハンズオンコードでSupabase Backend as a Serviceを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Supabase Backend as a Serviceを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのSupabase Backend as a Serviceは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン2/3です。

「RLSのテストとデバッグ」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このSupabase Backend as a Serviceレッスンでコードを書いて実行できますか？

はい。すべてのSupabase Backend as a Serviceレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

  1. RLSポリシー入門
  2. RLSのテストとデバッグ
  3. RLSとカスタムクレームによるロールベースアクセス
← Supabase Backend as a Serviceに戻る