{error.message}
}\nuser:
\n{JSON.stringify(user, null, 2)}\n client-side data fetching with RLS
\n{JSON.stringify(data, null, 2)}\n \n );\n};\n\nexport default LoginPage;\n```\n\n### Server-side rendering (SSR) - withPageAuth\n\nIf you wrap your `getServerSideProps` with `withPageAuth` your props object will be augmented with the user object.\n\n```js\n// pages/profile.js\nimport { withPageAuth } from '@supabase/auth-helpers-nextjs';\n\nexport default function Profile({ user }) {\n return {JSON.stringify(data, null, 2)}\n {JSON.stringify(user, null, 2)}\n \n );\n}\n\nexport const getServerSideProps = withPageAuth({\n redirectTo: '/',\n async getServerSideProps(ctx) {\n // Run queries with RLS on the server\n const { data } = await supabaseServerClient(ctx).from('test').select('*');\n return { props: { data } };\n }\n});\n```\n\n### Server-side data fetching to OAuth APIs using `provider_token`\n\nWhen using third-party auth providers, sessions are initiated with an additional `provider_token` field which is persisted as an HTTPOnly cookie upon logging in to enabled usage on the server side. The `provider_token` can be used to make API requests to the OAuth provider's API endpoints on behalf of the logged-in user. In the following example, we fetch the user's full profile from the third-party API during SSR using their id and auth token:\n\n```js\nimport { User, withPageAuth, getUser } from '@supabase/auth-helpers-nextjs';\n\ninterface Profile {\n /* ... */\n}\n\nexport default function ProtectedPage({\n user,\n data\n}: {\n user: User,\n profile: Profile\n}) {\n return