I have a feeling that I need to finish my auth flow differently, making sure to issue the

signinUser

mutation server-side instead of browser-side as I did now. Then it's the server which will receive the token and can store it in a session in some way.

Probably a good start to think about it.

Although, does the signinUser mutation accept unhashed credentials? If so, that might present a security risk...

@sam

signinUser

accepts an auth token coming from auth0 (in my case) and then exchanges it for a user token. So it's hashed AFAIK (although that's a term new for me -- learning along the way)

Ah, okay. As long as the user isn't sending their password unencrypted, it should be fine...

OK so now I guess I need to learn about calling cookie-parser by myself (next doesn't yet allow tweaking middleware) and storing server-side in-memory as a first step

jeez why is authentication and session management so complicated, can't we just all hold each other's hands and trust people when they say who they are? 😛

@sdubois this may help: https://medium.com/@miksago/cookies-sessions-and-authentication-a-new-approach-in-node-js-3414b6be7fdd

n.b., it's a private draft atm; I need to re-author it

I'll likely do something on password management as well, as it's a topic many people using node.js still have issues with

e.g., it's really good to version your password storage; such that you can easily do rolling migrations to newer stronger algorithms or address security concerns as they arise

@schickling is the title of this video intended to be "Apollo/React"?

thanks @thisismissem I'll read that

You're totally right, @sashko. Just fixed the name 🙂

any demo for apollo + ionic 2 (angular 2) ?

we got an instagram app with apollo + angular 2: https://github.com/graphcool-examples/angular-apollo-instagram-example simple smile

thanks

or a Todo app with the same stack. check https://medium.com/@gerard.sans/graphql-and-the-amazing-apollo-client-fe57e162a70c if that sounds good 😛

do you know an extension in vscode that would allow syntax highlighting , linting etc on gql es6 template strings? The author of one of the extensions (from apollostack) for graphql has raised an issue on vscode regarding this https://github.com/Microsoft/vscode/issues/5961 . I don't know if its has been resolved or anyone has found a solution

Should Graphcool create a channel in https://graphql.slack.com/ ?

E.g scaphold has one (but not active)

interestingly there's no Apollo channel either. Would probably just confuse people as they have their own slack (like here)

Good point @sdubois! Do you think it would provide some value to people having a channel there?

@schickling: only way to know is to try I guess... Maybe create a channel and leave a description suggesting asking questions either there or in this slack, as people prefer

hello

@sdubois: Totally 🙂

Hey @denisnikulin!

how do I download the schema I created in graph.cool?

🙂

You mean as a

.json

file?