Help me understand third party auth and storing user information
Do most apps that use third party auth still maintain their own Users table?
I have very little experience on backend/auth so lack a fundamental understanding of how this works, but the basic examples I've followed using Clerk simply displays the currently logged in users name and email address which is stored in the JWT so I'm uncertain if I'm missing something where a Users table isn't actually required.
Say for instance I have a blog with multiple authors/users and I wanted a page that displayed a list of all posts and the name of the user who posted it. To get the names of all the post authors, how would you do this? I'm guessing this means also maintaining a Users table which duplicates the user meta data any time a user signs up. This I guess would also give the flexibility of adding additional things like: username, date of birth, favourite Pokemon, etc.
Is this duplcating user data into Users table handled in the auth call back every time a user logs in (i.e. check if user exists in DB and create them if they don't), or is this done elsewhere?
FWIW: I'm using WorkOS AuthKit for auth.
0 Replies