With Auth0 it’s pretty much mandated to be one flow, unless you want to reimplement a lot of their login widget.

Bit of a faff having to handle this, an idempotent mutation would be great

Now my api interaction goes from declarative to procedural, which is a shame as graphql is really nice and declarative otherwise

I see what you are saying. Quick question - does your Auht0 lock look like this? Wouldn't it be trivial to only call the createUser mutation in the signup flow?

Quite often, we find, people want to ask for extra information when signing up a new user. As this information is required, there is no way to unify that in the schema.

Simpler flow 🙂

aha 🙂

I can rework my query code to treat this error as an OK

A shame I need two different query executor thingies now, but that’s fine 🙂

Not quite what I want, but that’s the nature of third party software. Otherwise it’s great 😄

Ok, that should be a decent workaround. What would work better for you in this case - to have a mutation you could call with a Auth0 id_token that always succeeds wether the user exists or not, or to just be able to use the id_token directly in the Authorization header, and Graphcool automatically creates a user if doesn’t exist?

set the channel topic: Flexible backend platform combining GraphQL+ AWS Lambda

Oh the latter would be even better

What a nice idea

How would you tell that the token is an auth0 token?

On your side

We validate it against the secret you provide when setting up the Auth0 Auth Provider. Would you mind creating a feature request for this? https://github.com/graphcool/feature-requests/issues

ooh nice.

I’m thoroughly impressed with the graph.cool team so far 😄

Thanks bowtie

hi @scott 🙌

hey @artyom how are you? 🙂

there’s @theom !! 🙌 hello! graphcool

Not sure if I’m just missing it, but is there a way to set permissions based on ownership rather than just a user being authenticated?

For example, I have a User model and a Contacts model, but only want authenticated users to be able to view their contacts

@scott This is currently part of our Beta Program. Please ping @nilan to join the program

oh, ok perfect, thanks 🙂

@artyom Greetings 👍