Replies: 1 comment 3 replies
-
|
You can't use any auth calls if you don't use auth. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
My project require me to use a custom auth flow. For some reasons, my company insist to do the email password authentication on our own without using supabase auth. I created an users table on my supabase to store users data instead of utilizing the users schema that provided by supabase. The idea is that I need to handle the auth and generate custom jwt claim. I also need to add organization_id to my app_metadata on my custom claim. So I don't really need any use for the sub, I only need the organization_id
After that I create a client session for each call:
I use my supabase JWT_TOKEN from setting and tried this. But I got:
I got the idea from some old article from 2023. Does it mean that we can't create our own jwt anymore? Or did I just miss something?
Does it because I mess with the session flow? Because I handle the register and login myself I didn't get the session_id, so I just put some random id there
Beta Was this translation helpful? Give feedback.
All reactions