Thanks for that, without going into ACL, I guess having a logoutUser resolver that adds the revoked token to a blacklist then having a permission query for all models that checks the current auth token against this blacklist would work.

Yeah you could have is user token enum id,id,id role role

and then mutate authorizations in and out

even time expire

we have all the ids a user is owner of .. then all the ids a user is admin of .. and then flags for auth roles

For time expiration I can rely on the token's

exp

prop

I use a serverless function in lambda .. to expire my own tokens .. but you could do a prop exp with a library like react timer

Agartha also created a lock library - https://github.com/kbrandwijk/graphcool-mutex

I find I keep rearchitecting over and over to use simple relationships .. and make it logic agnostic as possible

which reduces my calls, and makes secuirty and lookups more functional

mostly because im a complete noob to graph

graphcool-mutex

is for database locks for concurrency support, has nothing to do with tokens

Yup, it looks very cool too I'm going to use that 🙂

The problem with blacklisting auth tokens is that there is no token identification in the Graphcool token (no

jti

), so it's a bit harder to blacklist tokens.

Yup, I guess checking against the token itself would work

I use locks to stop paralell errors in a token db

but yeah .. brain threads

hello, I followed this tutorial https://www.howtographql.com/react-apollo/8-subscriptions/ to add subscription to my current project - I receive an ack and some ka but i’m not getting any data - after testing in the playground and looking at the ntwk packet i see that my apollo client sends the connection_init type but not the ‘start’ type. - the query is exactly the same i’m using in the playground - can anyone enlighten me as to what’s happening here?

I’m getting a log response like this:

2017-11-17T02:47:25.099Z 2546ms FAILURE {
  "error": "There was a problem parsing the function response. Function name: PublishImmediately"
}

and I can’t figure out why

Looks like extremely long execution times

invoking the function locally worked fine

It’s a subscription, and the subscription runs fine and fires as expected in the playground

And even worse, it looks like it just worked, (the intended outcome occurred, the post was published), but the log still shows the same error.

is it possible to do a type that relate to himself in a recursive way?

Does anyone know of a workaround for decoupling an app in GC from integrations? Specifically, I can’t disable Algolia. Thanks!

hey all, quick one for you - it seems like some of my Types have the createdAt and updatedAt fields and some don't. Was this something that changed recently or am I missing something?

is there any step by step guide how to run local server?

Hello all.. is anyone else experiencing problems with subscriptions? I am mutating an object (result of mutation is what is expected) but subscription is triggered with old data https://www.dropbox.com/s/dnjk5a4gbxhvfzt/Screenshot%202017-11-17%2013.10.05.png?dl=0

Anyone else still getting 504 errors when deploying?