Prisma

also for the user authentication scenario is there a way I can do a user upsert in one graphql call.. or do some sort of if condition so that I create user if it doesn’t exist and call signin again?

because when I use auth0 lock, I get a user token but don’t know if its an existing user or not

I suppose I can try signing in first - then look for a non exiting user error (is it code 3022?) and then do a create mutation then a signin mutation again

but wondering if there’s a shorter or more reliable way of doing it

There is <@U327M1E6P>! We'll release a new way of doing this over the next few days!

calling the createUser mutation with auth0, how do I pass along additional required fields that I set on my user model?

```
 createUser(authProvider: { auth0: { idToken: $idToken }}, email: $email, username: $username) {
      id
    }
```

do I send it as part of the authProvider object?

I am currently working on a detailed example, also with the situation that we have to set additional required fields with `createUser` :simple_smile:

will be ready today. I am also using Apollo :+1:

I sent it as the above query as a seperate parameters but it gave me a permission error

do you have a permission for `EVERYONE` on `createUser`?

it’s got no permissions set on it so it would be the default

I’ll set it to everyone and see what happens

well, a request is permitted if a permission is found whose parameters this request fulfills

I’m also toying with the idea of using an auth0 rule to create users on signup

if you have no permissions, we cannot grant the request permission :simple_smile:

and have the backend do it rather than the client.. auth0 would have to call an http endpoint but not sure how to get the auth0 token from the rules context that they have...

<@U0RQY0KK5> setting the permissions worked… for some reason it makes me a bit nervous to allow everyone to create - but I guess that’s the right permissions for a registration from a client use case

yes, it feels weird, but it's perfectly fine :simple_smile: we definitely should allow users to sign up, right :simple_smile:

is there a way I can create a user and set the auth0UserId directly without using a token?

If I move the createUser from the client code to the server by using an auth0 “rule” server side trigger, I can post to graph cool auth0userid with an admin permanent token

However, I don’t think the auth0 context gives me access to the idToken that would have been generated

no, the `auth0UserId` is automatically set by the `createUser` mutation depending on the `idToken` that you provide

is there a way that an admin account can insert into the user data directly with a different mutation?

no, there isn't. Can you speak a bit more about your use case for this possibility?