Meta tags:

Headings (most frequently used words):

and, dgraph, schema, auth, example, adapter, resources, setup, installation, environment, variables, configuration, unsecure, secure, authorization, verificationkey, jwtsecret, header, authheader, the, nextauth, secret, jwt, session, directive, about, js, download, acknowledgements,

Text of the page (most frequently used words):
auth (45), the (37), string (36), dgraph (28), nextauth (27), rule (23), true (21), you (19), env (19), #schema (18), your (15), jwt (15), #secret (15), process (15), user (15), and (14), import (14), adapter (13), type (12), hash (12), search (12), authorization (10), session (10), from (10), dgraphadapter (9), jwtsecret (9), this (8), add (8), header (8), authheader (8), field (8), hasinverse (8), token (7), query (7), unsecure (7), for (6), next (6), can (6), update (6), secure (6), here (6), datetime (6), are (5), hs256 (5), userid (5), const (5), with (5), use (5), default (5), delete (5), providers (5), github (4), signout (4), signin (4), export (4), verificationkey (4), namespace (4), expires (4), sessions (4), account (4), accounts (4), example (4), auth_header (4), omit (4), following (4), properties (4), running (4), authtoken (4), endpoint (4), meta (4), azure (4), better (3), npm (3), want (3), directive (3), dgraphclient (3), made (3), types (3), used (3), custom (3), dgraph_graphql_key (3), dgraph_graphql_endpoint (3), app (3), express (3), src (3), installation (3), resources (3), getting (3), started (3), discord (2), security (2), introduction (2), drizzle (2), cloudflare (2), defined (2), set (2), will (2), allow (2), define (2), part (2), algorithms (2), return (2), async (2), decode (2), algorithm (2), sign (2), encode (2), handlers (2), securely (2), database (2), customize (2), using (2), order (2), requests (2), within (2), have (2), each (2), bottom (2), provide (2), algo (2), graphql (2), identifier (2), verificationtoken (2), image (2), emailverified (2), email (2), name (2), queryuser (2), filter (2), sessiontoken (2), session_state (2), id_token (2), scope (2), access_token (2), refresh_token (2), token_type (2), accesstoken (2), int64 (2), expires_at (2), refreshtoken (2), provideraccountid (2), provider (2), production (2), access (2), main (2), not (2), expressauth (2), routes (2), sveltekitauth (2), sveltekit (2), qwikauth (2), qwik (2), auth_dgraph_graphql_key (2), auth_dgraph_graphql_endpoint (2), configuration (2), environment (2), variables (2), bun (2), yarn (2), pnpm (2), setup (2), adapters (2), page (2), identity (2), credentials (2), inc, 2026, contributors, acknowledgements, download, community, about, once, settings, every, rules, verify, days, expiresin, strategy, jsonwebtoken, only, works, rs256, interact, must, functions, hs512, further, roles, implement, rbac, logic, verificationrequest, generated, injected, interacting, anonymous, system, allows, interactions, all, required, specify, login, register, tells, where, lookup, headers, incoming, server, configure, file, same, property, when, instantiate, key, app_secret, backend, object, values, deployments, restrict, form, control, via, alongside, adapted, based, upon, our, approach, does, require, quickest, way, applying, instance, paste, codebox, cloud, local, trust, proxy, route, handle, usesignout, usesignin, usesession, onrequest, plugin, auth_secret, abc123, http, localhost, 8080, install, documentation, edit, question, give, feedback, migrating, integrations, xata, upstash, redis, unstorage, typeorm, surrealdb, supabase, sequelize, prisma, pouchdb, postgresql, neon, neo4j, mongodb, mikroorm, kysely, hasura, firebase, firestore, faunadb, edgedb, dynamodb, tables, zoom, zoho, zitadel, yandex, workos, wordpress, wikimedia, webex, vipps, mobilepay, united, effects, twitter, twitch, trakt, todoist, tiktok, threads, strava, spotify, slack, simplelogin, sendgrid, salesforce, sailpoint, resend, reddit, postmark, pipedrive, pinterest, patreon, passkey, passage, osu, osso, onelogin, okta, notion, nodemailer, nextcloud, netsuite, netlify, naver, microsoft, entra, medium, mattermost, mastodon, mailru, mailgun, mailchimp, loops, logto, linkedin, line, keycloak, kakao, instagram, server4, hubspot, google, gitlab, fusionauth, frontegg, freshbooks, foursquare, forwardemail, figma, faceit, facebook, eveonline, duende, server6, dropbox, dribbble, descope, coinbase, cognito, click, bungie, boxyhq, saml, box, bitbucket, beyondidentity, battlenet, bankid, norge, devops, b2c, authentik, auth0, asgardeo, apple, school, connections, typescript, deployment, pages, protecting, get, management, webauthn, magic, links, oauth, authentication, migrate, light, ask, concepts, api, reference, guides, project, now, skip, content,

Text of the page (random words):
auth js dgraph skip to content the auth js project is now part of better auth auth js getting started guides api reference concepts security ai ask ai github 22 2k light introduction migrate to better auth getting started installation authentication oauth magic links credentials webauthn database session management signin and signout get session protecting resources custom pages deployment typescript connections providers 42 school apple asgardeo auth0 authentik azure ad azure ad b2c azure devops bankid norge battlenet beyondidentity bitbucket box boxyhq saml bungie click up cognito coinbase credentials descope discord dribbble dropbox duende identity server6 eveonline facebook faceit figma forwardemail foursquare freshbooks frontegg fusionauth github gitlab google hubspot identity server4 instagram kakao keycloak line linkedin logto loops mailchimp mailgun mailru mastodon mattermost medium microsoft entra id naver netlify netsuite nextcloud nodemailer notion okta onelogin osso osu passage passkey patreon pinterest pipedrive postmark reddit resend sailpoint salesforce sendgrid simplelogin slack spotify strava threads tiktok todoist trakt twitch twitter united effects vipps mobilepay vk webex wikimedia wordpress workos yandex zitadel zoho zoom adapters azure tables cloudflare d1 dgraph drizzle dynamodb edgedb faunadb firebase firestore hasura kysely mikroorm mongodb neo4j neon postgresql pouchdb prisma sequelize supabase surrealdb typeorm unstorage upstash redis xata integrations migrating to v5 on this page resources setup installation environment variables configuration unsecure schema example secure schema example dgraph authorization verificationkey and jwtsecret header and authheader the nextauth secret jwt session and auth directive question give us feedback edit this page on github getting started adapters dgraph dgraph adapter resources dgraph documentation setup installation npm pnpm yarn bun npm install auth dgraph adapter pnpm add auth dgraph adapter yarn add auth dgraph adapter bun add auth dgraph adapter environment variables auth_dgraph_graphql_endpoint http localhost 8080 graphql auth_dgraph_graphql_key abc123 configuration next js qwik sveltekit express auth ts import nextauth from next auth import dgraphadapter from auth dgraph adapter export const handlers auth signin signout nextauth providers adapter dgraphadapter endpoint process env auth_dgraph_graphql_endpoint authtoken process env auth_dgraph_graphql_key you can omit the following properties if you are running an unsecure schema authheader process env auth_header default authorization jwtsecret process env auth_secret src routes plugin auth ts import qwikauth from auth qwik import dgraphadapter from auth dgraph adapter export const onrequest usesession usesignin usesignout qwikauth providers adapter dgraphadapter endpoint import meta env dgraph_graphql_endpoint authtoken import meta env dgraph_graphql_key you can omit the following properties if you are running an unsecure schema authheader import meta env auth_header default authorization jwtsecret import meta env secret src auth ts import sveltekitauth from auth sveltekit import dgraphadapter from auth dgraph adapter export const handle signin signout sveltekitauth providers adapter dgraphadapter endpoint process env dgraph_graphql_endpoint authtoken process env dgraph_graphql_key you can omit the following properties if you are running an unsecure schema authheader process env auth_header default authorization jwtsecret process env secret src routes auth route ts import expressauth from auth express import dgraphadapter from auth dgraph adapter const app express app set trust proxy true app use auth expressauth providers adapter dgraphadapter endpoint process env dgraph_graphql_endpoint authtoken process env dgraph_graphql_key you can omit the following properties if you are running an unsecure schema authheader process env auth_header default authorization jwtsecret process env secret unsecure schema the quickest way to use dgraph is by applying the unsecure schema to your local dgraph instance or if using dgraph cloud you can paste the schema in the codebox to update ️ this approach is not secure or for production use and does not require a jwtsecret this schema is adapted for use in dgraph and based upon our main schema example type account id id type string provider string search by hash provideraccountid string search by hash refreshtoken string expires_at int64 accesstoken string token_type string refresh_token string access_token string scope string id_token string session_state string user user hasinverse field accounts type session id id expires datetime sessiontoken string search by hash user user hasinverse field sessions type user id id name string email string search by hash emailverified datetime image string accounts account hasinverse field user sessions session hasinverse field user type verificationtoken id id identifier string search by hash token string search by hash expires datetime secure schema for production deployments you will want to restrict the access to the types used by next auth the main form of access control used in dgraph is via auth directive alongside types in the schema example type account auth delete rule nextauth eq true add rule nextauth eq true query rule nextauth eq true update rule nextauth eq true id id type string provider string search by hash provideraccountid string search by hash refreshtoken string expires_at int64 accesstoken string token_type string refresh_token string access_token string scope string id_token string session_state string user user hasinverse field accounts type session auth delete rule nextauth eq true add rule nextauth eq true query rule nextauth eq true update rule nextauth eq true id id expires datetime sessiontoken string search by hash user user hasinverse field sessions type user auth query or rule query userid string queryuser filter id eq userid id rule nextauth eq true delete rule nextauth eq true add rule nextauth eq true update or rule query userid string queryuser filter id eq userid id rule nextauth eq true id id name string email string search by hash emailverified datetime image string accounts account hasinverse field user sessions session hasinverse field user type verificationtoken auth delete rule nextauth eq true add rule nextauth eq true query rule nextauth eq true update rule nextauth eq true id id identifier string search by hash token string search by hash expires datetime dgraph authorization verificationkey your jwt secret here header your auth header here namespace your custom namespace here algo hs256 dgraph authorization in order to secure your graphql backend define the dgraph authorization object at the bottom of your schema and provide authheader and jwtsecret values to the dgraphclient dgraph authorization verificationkey your jwt secret here header your auth header here namespace your custom namespace here algo hs256 verificationkey and jwtsecret this is the key used to sign the jwt ex process env secret or process env app_secret header and authheader the header tells dgraph where to lookup a jwt within the headers of the incoming requests made to the dgraph server you have to configure it at the bottom of your schema file this header is the same as the authheader property you provide when you instantiate the dgraphclient the nextauth secret the nextauth secret is securely generated using the jwtsecret and injected by the dgraphadapter in order to allow interacting with the jwt dgraphclient for anonymous user requests made within the system ie login register this allows secure interactions to be made with all the auth types required by next auth you have to specify it for each auth rule of each type defined in your secure schema type verificationrequest auth delete rule nextauth eq true add rule nextauth eq true query rule nextauth eq true update rule nextauth eq true jwt session and auth directive dgraph only works with hs256 or rs256 algorithms if you want to use session jwt to securely interact with your dgraph database you must customize next auth encode and decode functions as the default algorithm is hs512 you can further customize the jwt with roles if you want to implement rbac logic auth js import nextauth from next auth import as jwt from jsonwebtoken export const handlers auth signin signout nextauth session strategy jwt jwt secret process env secret encode async secret token return jwt sign token userid token id secret algorithm hs256 expiresin 30 24 60 60 30 days decode async secret token return jwt verify token secret algorithms hs256 once your dgraph authorization is defined in your schema and the jwt settings are set this will allow you to define auth rules for every part of your schema cloudflare d1 drizzle about auth js introduction security discord community download github npm acknowledgements contributors auth js better auth inc 2026