Clerk authorization custom implementation.
I am trying to implement an authorization flow for one of the in development app we are building. Basically i am able to implement clerk sign in via their out of the box components. But i noticed since the app is publicly hosted via vercel and open in the public anyone can sign in or sign up using clerk through github or google login.
Wanted to make a authorization flow where if the users signing in are emails stored in the db they can get access to the ui if not i would like them to get redirected to a different website. So far tried to implement that but i am having an issue where clerk publishable key is not being read. Not sure if is a clerk limitation, since i don't want to pay their premium feature for blocking or authorizing specific users.
Any suggestions? The app is still in development but also already deployed on vercel so wondering if it is smth that can be done or if is a wrong approach.
0 Replies