GraphQL Auth without Middleware

1

JSON Web Token

Since GraphQL is a stateless API, it does not create sessions between the client and the API. The common method to authorize clients to query or mutate data is by passing a token known as a JSON Web token (JWT). The common way for a client to obtain a JWT is by authenticating through some auth provider who returns a JWT to the client. This JWT then provided by the client to the GraphQL API in the request is used in the GraphQL API to authorize actions to perform create, read, update, and delete (CRUD) operations on data.

#Identity Provider #Identity And Access Management #SSO 276 social mentions

2

Dgraph

In almost every GraphQL API, GraphQL developers need to add middleware to create rules for the authorization of these CRUD actions. There is on implementation of GraphQL however that stands above the competition, Dgraph! Dgraph has engineered their GraphQL API which is embedded into the core of the database to generate CRUD operations with authorization built-in. How is this possible? When a developer deploys a schema, they simply need to create rules using the @auth directive. Dgraph will then apply these rules and run them as a single query operation (avoiding the N+1 problem) when querying and mutating data.

#Graph Databases #Databases #NoSQL Databases 20 social mentions