Prisma

I would try it in a new project, and if the problems persist, report them. I'm off to bed too now, good luck...

nope… doesn’t work in a new project either

does graphcool support RS256 tokens from auth0?

hmmm looks like no <https://github.com/graphcool/feature-requests/issues/145>

however the latest version of auth0-js (v8) requires it... <https://www.npmjs.org/package/auth0-js>

what worries me is that v8 auth0-js has been out since december last year, and graphcool still does not support it

so I guess I'll have to downgrade to auth0-js v7, which hasn't been updated since January

<@U63RJH69E> the latest version of Auth0 Lock still supports HS256 - I'm using that to do authentication until graph.cool supports RS256. I'd rather be using RS256 but at least Auth0 Lock is an up to date library.

<@U5ZDXT94Z> I'm using `auth0-js` which is not the same as Auth0 Lock (as I need to build a custom auth UI)

I started out using auth0-js but switched when I his the RS256 issue. I'm only using lock until RS256 support is available. Lock does provide some customisation but it would be good to have the full set of options

definitely would be great if they supported more customizations out of the box

I have a working implementation of auth0-js v8 returning hs256 tokens and graphcool. So it can work and is supported. However  auth0 might deprecate  hs256 soon.

The trick for me was just initializing auth0-js with this:
```
  auth0 = new auth0.WebAuth({
    domain: AUTH_CONFIG.domain,
    clientID: AUTH_CONFIG.clientID,
    redirectUri: AUTH_CONFIG.callbackUrl,
    responseType: 'token id_token',
  });
```

Adding for example scope here will lead to auth0 returning a rs256 type id_token.

I use `auth0.authorize()` which sends me to the hosted login pages.

thanks <@U5W58040J> will give it a try. The readme does say though that rs256 must be used. and when i tried with hs256 the hash parsing would throw an error

Yeah, the autoParse is the part that's not supported for hs256. But, it's not very complicated to retrieve the token with e.g. `query-parser` from the callback hash.

not great to be using older outdated libraries when dealing with security &amp; auth

Thanks, updated this feature request - <https://github.com/graphcool/feature-requests/issues/145>

What would be the best way to fetch additional data about a user that has just authenticated with auth0

I get back an id token which I can use to call createUser, but I want their name, email, profile picture in the Graphcool node

I could request those details be added in the token, but prefer to keep size of the JWT token down.

I could use a function and have the client pass dummy values which are transformed, that doesn't seem right though.

I guess i'll use auth0 to auth, then fetch user details again from auth0 then send to graphcool

<@U63RJH69E> that's likely the best approach, yes

you shouldn't need to do an extra request to auth0 to get the details - if you set the scope for the authentication request to the right value, you will get those details in the authentication response

e.g. I use "openid email name" to get the email address and user name, which I then add to the graph.cool database

It looks like you want "openid profile" which should return everything you want

If you're using auth0 Lock, the code looks like this:

var options = {
      auth:{
        params:{
          scope: 'openid email name'
        }
      }

    };

    this._lock = new Auth0Lock(AUTH_CONFIG.clientId, AUTH_CONFIG.domain, options)

<@U5ZDXT94Z> does this not also encode the requested fields in the JWT token?

Yes, it includes the requested claims in the token

<@U5ZDXT94Z> I'm trying to keep the size of the JWT to a minimum, but thanks for the heads up!

Hi! I have a lot of google accounts and I can't remember which one I used fo my project... my project Id is cj3n0fa4147rf0173ledl3s1i and i keep falling on the start page

Has anyone used Functions to do cascading of deletes (i.e. delete instances of TypeB that are related to TypeA when an instance of TypeA is delete)?

<@U5ZDXT94Z> I’ve used Google Cloud Functinos to update some statistics based on mutations to a type

Deploy the function, the the lokka library to write your queries, and profit :slightly_smiling_face:

makes sense - so basically the function is just a client, presumably authenticating with a permanent auth token?

Precicely - you can create permantent auth tokens for your backend functions in the project settings

The only drawback is that for each mutation that triggers this callback, you will end up with another request towards your billing

Or in general, has anyone used Functions to make extra changes to the graph.cool database that are triggered from a mutation?

<@U5ZDXT94Z> yes i have done this. You can see the example here <https://github.com/graphcool-examples/functions/tree/master/stripe-create-customer-es6>

I created a customer and then updated it in my sss function

Thanks <@U59R4DB42> - that's exactly the kind of example I was looking for.

No worries! I wrote a blog abt that example too if you are interested <http://www.reactjunkie.com/graphcool-functions-in-es6-with-async-await/>

hello! do you guys have a recommended guide on using relay modern with your service?

<@U643ZS4S2> indeed! <https://www.graph.cool/docs/tutorials/relay-modern-getting-started-woodito7ug/>

just a couple notes as i'm going through this

would be good to notify the user he'll get errors when you start adding fragments. the project recompiles automagically, so you immediately get errors and it freaked me out

also running on windows, relay-compiler doesn't immediately attach to the path, may be confusing for those users. running ./node_modules/relay-compiler/bin/relay-compiler works fine

also, the default "playground" for me was "simple", and the mutations didn't work there. had to change to relay

<@U643ZS4S2> that's great feedback could you please create a new issue here to persist it? <https://github.com/graphcool/content/issues> :simple_smile:

sure thing. feedback submitted <https://github.com/graphcool/content/issues/207>

while  i define a server side subscription is it possible to make a query to another table

currently only the updated node is accessable

<@U63BV7D89> u can easily use fetch or graphql-request to query any other types in your sss function 

<@U59R4DB42> ......subscription {
  Event(filter: {
    mutation_in: [CREATED, UPDATED, DELETED]
  }) {
    updatedFields
    node {
      id
      token
    }
  }
}

i need to access the parameter token from all the node in that table

hey team :wave: is there any timeframe for when password reset will be added to email/password auth? it's becoming a real blocker for us! would be great to get an idea of when it will be ready.

<@U3KMWQYBA> <@U5GP52J14> hey, we're looking to test a custom authentication feature with a small beta group sometime this week that would also include the possibilty to build your own password reset feature and verification email workflow :slightly_smiling_face:

could we be included in the beta? would love to try it out :smiley_cat:

That’s a big blocker for us too. Love to be on the beta!

I'm sorry but for now all spots are already occupied for the email password beta :slightly_smiling_face:

I’ve very happily outsourced all my password reset to Auth0: <https://blog.graph.cool/user-authentication-in-graphql-with-auth0-digits-4ce01788950>