Third party authenticator
Hello! Im building a website for our e-sports center and I was thinking about using a third party authenticator like Clerk or Vipps. That's great as we don't need to store user data ourself, but as we are going to sell stuff, we need some form of user data to connect the purchases to the user. What is the best way to do do this? Is it just to create a user table in Postgres and only have a user_id column? Or is there a better way?
1 Reply
When a user is created in clerk. An event is created and you can create wehhooks to sync your back end with clerk users.
You would create a user table in your backend. With an external ID column. You create an API endpoint that will listen to the user created web hook event. You'll then create the user when a new users created.