Authdog

Gatsby

Authentication for Gatsby, client and Functions

Add auth with a React client provider and server helpers for Gatsby Functions. Sessions use the same cookie and OIDC flow as every other Authdog SDK, so one environment works across your stack.

Start buildingRead the docs
npmlatestCI passing
One provider
wrapRootElement in gatsby-browser.js and gatsby-ssr.js is all it takes to make session state available everywhere.
Four server helpers
getSession, getUser, requireAuth, and logout cover the whole server-side auth surface from src/api routes.
HttpOnly session cookie
Tokens are validated against the trusted identity host and sessions ride secure, HttpOnly cookies read on the server.
One shared session
The same cookie and OIDC userinfo flow as every other @authdog/* package.

Client provider

// gatsby-browser.js
import { AuthdogProvider } from "@authdog/gatsby/client"

export const wrapRootElement = ({ element }) => (
  <AuthdogProvider>{element}</AuthdogProvider>
)

Protect a Gatsby Function

// src/api/me.ts
import { createAuthdog } from "@authdog/gatsby/server"

const authdog = createAuthdog({ publicKey: process.env.PK_AUTHDOG! })

export default authdog.requireAuth((req, res) => {
  res.json(req.authdog.user)
})

Client provider meets Functions

Everything Gatsby apps need

A provider for the browser and typed helpers for Gatsby Functions: session state in the UI, real enforcement on the server.

01

Client provider

Wrap wrapRootElement in gatsby-browser.js and gatsby-ssr.js once, and session state is available across every page and component.

  • Browser and SSR
  • Every page and component
02

Gatsby Functions

createAuthdog() gives you getSession, getUser, requireAuth, and logout as first-class helpers inside src/api routes.

  • src/api routes
  • Four helpers
03

Real server enforcement

requireAuth is the enforcement point. It validates the session in your Functions before the handler ever runs.

  • Validated before your handler
  • Server-side only
04

One shared session

Uses the same authdog-session cookie and OIDC userinfo flow as every other @authdog/* package, so one environment spans your stack.

  • Same cookie everywhere
  • One environment
05

SSR-friendly bootstrap

The provider strips the login redirect's ?token= and reloads once so the server can persist the HttpOnly session cookie.

  • Cleans the redirect URL
  • Persists on the server
06

Fully typed

req.authdog.user is typed end to end inside Functions, and the client hooks are typed for your components.

  • Typed Functions
  • Typed client hooks
01

Install

Add @authdog/gatsby and your environment keys.

02

Wrap the root

Add the provider to gatsby-browser.js and gatsby-ssr.js.

03

Protect Functions

Wrap src/api handlers in requireAuth.

Add auth to your Gatsby site.

Install the SDK, wrap your root element, and protect your Functions today. Free to start, with secure defaults built in.

Start Building