This message was deleted.
# prisma-whats-new
s
This message was deleted.
n
@quadsurf you don't need the signinUser mutation with Auth0, you can use the token you get from Auth0 directly
q
not sure what you mean… how so? so if I just use “updateOrCreateUser”, pass in the Auth0 idToken, this has the effect of both updating/creating, and signing the user in? no need to pass in bearer tokens for ensuing CRUDing mutations? assuming permissions are right, i can freely begin CRUDing without bearer tokens? thank you btw for the help… much much appreciated
does the Auth0 idToken have to be present in every single future mutation i make?
n
I'm not talking about
updateOrCreateUser
. Calling
createUser
with an
idToken
creates a new user with the corresponding auth0UserId. Now, whenever a request to your API contains a valid token as the
Authorization
header that corresponds with the auth0UserId of a registered user in your Graphcool project, that request is considered authenticated
so, you do need to set the bearer token as the authorization header 🙂
but
signinUser
mutation is not necessary, as you can use the idToken for that