Clerk logo

Clerk Docs

Ctrl + K
Go to


Learn how to integrate Clerk into your Next.js + Supabase application

Getting started

The first step is to create a new Clerk application from your Clerk Dashboard if you haven’t done so already. You can choose whichever authentication strategy and social login providers you prefer. For more information, check out our Set up your application guide.

After your Clerk application has been created, use the lefthand menu to navigate to the JWT Templates page.

Click on the button to create a new template based on Supabase.

This will pre-populate the default claims required by Supabase. You can include additional claims or modify them as necessary. Shortcodes are also available to make adding dynamic user values easy.

Note the name of the JWT template (which you can change) because this will be needed later.

Supabase requires that JWTs be signed with the H256 signing algorithm and use their signing key. You can locate the JWT secret key in your Supabase project under Settings > API in the Config section.

Reveal the JWT secret to copy it and then paste it in the Signing key field in the Clerk JWT template. ​​After the key is added, you can click the Apply Changes button to save your template.

Configure your client

To configure your client, you need to set some local environment variables. Assuming a React application, set the following:

Your Clerk Frontend API can be found on the Clerk Dashboard home in the API Keys section.

To get the ones needed for Supabase, navigate to the same Settings > API page as before and locate the anon public key and URL.​

Note: Supabase recommends enabling Row Level Security (RLS) for your database tables and configuring access policies as needed.

After setting those three environment variables, you should be able to start up your application development server.

Install the JavaScript client for Supabase with:

You can then initialize the Supabase client by passing it the environment variables and the access token from Clerk.


Access user ID in RLS policies

It is common practice to need access to the user identifier on the database level, especially when working with RLS policies in Postgres. Although Supabase provides a special function auth.uid() to extract the user ID from the JWT, this does not currently work with Clerk. The workaround is to write a custom SQL function to read the sub property from the JWT claims.

In the SQL Editor section of the Supabase dashboard, click New Query and enter the following:

This will create a requesting_user_id() function that can be used within an RLS policy.

For example, this policy would check that the user making the request is authenticated and matches the user_id column of a todos table.

Next steps

Was this helpful?

Clerk © 2022