getServerSideProps 上的 Supbase 策略 - Next.js

Question

I'm crafting a Trello clone with Next.js and Supabase as a BaaS.

const { data } = await supabase
    .from<BoardType>('board')
    .select('*')
    .eq('id', board.id)
    .single();

Answer 1

I found out it sends the request on the datebase with the anon key and not the authenticated jwt in the getSSProps. not sure why or if its intentional. If you add the role() = 'anon' rule it works, but that is not what you want in my opinion.

Answer 2

Might not be the best way, but this is how I solved it with some hints from this Github discussion https://github.com/supabase/supabase/discussions/1094#discussioncomment-714633

From my understanding, the Supabase client is a little different on the server compared to in the browser (no session). Pulling the token out of cookies and adding it to the client lets the requests to supabase be from the authenticated user.

export const getServerSideProps: GetServerSideProps = ({ req }) => {
  const { user, token } = await supabase.auth.api.getUserByCookie(req);
  supabase.auth.setAuth(token);

  const { data, error } = await supabase.from(...