todo-app-graphql-engine-auth0's Introduction

Important: This repo has been moved to hasura/graphql-engine

The contents of this repo have been moved to hasura/graphql-engine. Please create all issues and pull requests there.

Todo app using Hasura GraphQL Engine, Heroku Postgres and Auth0

STEP 1: Set auth0 domain

Set your auth0 domain in auth-webhook/constants.js. Also allow callbacks for http://localhost:3000/callback in your auth0 dashboard.
STEP 2: Deploy the auth Webhook (using ngrok, glitch, heroku or whatever)
STEP 3: Start GraphQL engine with the the auth-hook as the webhook URL and access key of your choice

Deploy GraphQL engine to Heroku if you do not have it deployed anywhere.
STEP 4: Apply the migrations
- Add your database URL and access key in hasura-graphql-engine/config.yaml
- Run hasura migrate apply to create the required tables and permissions for the todo app
Step 5: Set React app variables

Set auth0 domain, auth0 client ID and the GraphQL Engine URL in todo-app/src/constants.js
Step 6: Run the React app

Run npm start from the todo-app directory to start the TODO app.

THe app runs on port 3000 by default. You can change the port number, but you will also have to reconfigure the callback

todo-app-graphql-engine-auth0's People

Contributors

Stargazers

Watchers

todo-app-graphql-engine-auth0's Issues

Refer X-Hasura-User-Id in GraphQL mutations?

Consider this request payload when creating a todo.

{"operationName":"insert_todo","variables":{"objects":[{"task":"test-todo5","user_id":"auth0|5b721527280d8b73e2721281","completed":false}]},"query":"mutation insert_todo($objects: [todo_insert_input!]) {\n insert_todo(objects: $objects) {\n affected_rows\n returning {\n id\n task\n completed\n }\n }\n}\n"}

Is there a way to substitute the user_id field in a graphql mutation with a Hasura header value on the server side? Ideally with the X-Hasura-User-Id header that already has the same information(https://docs.hasura.io/1.0/graphql/manual/auth/index.html).

I am looking to avoid sending any more authentication/authorization information than I need to.