Using Supabase RLS with Trigger V3 | Trigger.dev | Page 1

cloud loom May 22, 2024, 11:46 AM

#

You can't call Trigger.dev directly from the client side (yet). We do have a plan for this in the future using pre-signed URLs, a bit like how S3 does it.

I think you just need to pass the authorization header value (opts.req.headers.authorization) in the payload to your trigger task. Then you can have a function that returns a userId and authenticated Supabase client.

We are working on adding middleware support which would allow you to easily share this logic, exactly like how tRPC does it. But that won't be available for a few weeks.

#

This does mean you'd need a Nest.js API endpoint though, or server action

#

that has access to the request object

cloud loom May 23, 2024, 7:47 AM

#

This doesn't work?

const supabase = createClient<Database>(
        process.env.NEXT_PUBLIC_SUPABASE_URL ?? '',
        process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY ?? '',
        {
          auth: {
            autoRefreshToken: false,
            detectSessionInUrl: false,
            persistSession: false,
          },
          global: {
            headers: {
              Authorization: input.authorization,
            },
          },
        }
      );

cloud loom May 23, 2024, 12:32 PM

#

Ok I understand. So I think you need to get the authorization value from the cookies and then pass that to the trigger function.

#

In your TRPCRouter can you do this?

const { data, error } = await supabase.auth.getSession()
const accessToken = data.session.access_token;

//trigger and pass the accessToken in

https://supabase.com/docs/reference/javascript/auth-getsession

#Using Supabase RLS with Trigger V3