-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: supabase auth middleware #861
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 10bcfb8 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
const secret = supabase ?? env<SupabaseEnv>(c).SUPABASE_JWT_SECRET | ||
const token = c.req.header('Authorization') | ||
|
||
if (!token) return c.json({ message: 'token is required' }, 401) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using HTTPException
is better than returning the response directly. You can refer to Basic Auth Middleware:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file is not needed for this PR.
Hi @ljh12138164 Sorry for the late reply. I've left the comments. Check them! |
This middleware adds check supabase auth to the context of each request.
i write a example in my repo.
and this example use Next.js and work well.