auth-helpers VS sk-auth

I have encountered a similar issue, but I haven't fully found a solution yet. Currently, I'm using the getSession function throughout my server components. Yesterday, I tried running a middleware to refresh the user's session, based on this example: https://github.com/supabase/auth-helpers/blob/main/examples/nextjs/middleware.tsx. This caught my attention because the comment mentioned that the middleware is necessary for any Server Component route using createServerComponentClient. Right now, I'm testing this approach, and so far, I haven't been logged out since yesterday. Do you have that in your application? The main difference between getSession and getUser in supabase is that getSession reads the cookies and is very fast (around 1-2 ms), while getUser makes a call to the supabase API with the access token to retrieve the user and I would assume they also verify the JWT on their end.

F.ex. Have a look how supabase-auth-helper-sveltekit works. This is the "SvelteKit way" to approach authentication. It also works perfectly with invalidate to reload or invalidate data that is connected to the current user session. As pointed out already, there is no reason you should not be able to access your JWT.

We have updated the Next.js Auth Helpers package to make it available across the client and server of the App Router. They also now implement server-side auth by default with PKCE - meaning the entire auth flow is now possible server-side.

Example

seems like known issue https://github.com/supabase/auth-helpers/issues/497

auth helper for sveltekit: https://github.com/supabase/auth-helpers/tree/main/packages/sveltekit

I do think checking auth in a server component would likely be better for your use here. Supabase has a nice example here: https://github.com/supabase/auth-helpers/tree/main/examples/nextjs-server-components They have a simple case with Middleware, but you wouldn't need to do it that way. Can use "redirect(/login)" from the server component.

I tried to develop authrization with Google Oauth via sk-auth. sk-auth is library of SvelteKit like NextAuth.

Just to update you on the situation, I have decided that my REST API will not deal with user sign-ups or sign-ins. It will basically respond to the requests coming with JWT tokens. My front-end client will do the user sign-ups and sign-ins. Once a user is authenticated I will be setting up an axios or request client with JWT token provided by AWS Cognito to query my back end API. In this case, I'm looking forward to try out Svelte and found a perfect package to do all that very easily which is sk-auth.

SvelteKitAuth (last commit the 2022-02-23)

Useful if true but I've just integrated sk-auth into my app...

For example https://github.com/Dan6erbond/sk-auth isn't as actively maintained now and doesn't run on CFW.

I have. Quite a bit, actually, as I'm the author of SKAuth which is an authentication library for SvelteKit and am also building a larger side project with Svelte.

I'd love to see you guys check out the GitHub repository, give the demo app a look and provide your feedback on what else you would like to see in this project!