I'm trying to set up Sign in with Apple with my Expo app and I have a general question about handling social logins with Prisma (or any back end, I guess). Right now, I have a signup mutation that expects a name, email, and a password. The password is hashed, the user is created, and a token is sent back (to be set in an auth header for future requests). When handling social logins, however, what's the best approach? There's obviously be no password sent during registration but I'll get a token in the payload from Apple. Should I just create a new mutation – one specific to a login like this – and create a user with the token stored under something like appleToken as opposed to a password or is there a better approach? I've never done anything like this so I'm learning as I go. Thanks! 🙂

I usually like to go with the latter (with an

appleToken

field + separate mutation). This allows for cases when you want to “connect” multiple social accounts to the same user. You could also identify a primary way to login in a different field called

loginType

or something

Thanks, @siddhant. 👍