# Authentication

@redwoodjs/auth is a lightweight wrapper around popular SPA authentication libraries. We currently support the following authentication providers:

# Installation

# CLI Auth Generator

The following CLI command will install required packages and generate boilerplate code and files for Redwood Projects:

yarn rw g auth [provider]

[provider] values can be either "netlify" or "auth0".

# Manual Install

# Netlify Identity Widget

cd web
yarn add @redwoodjs/auth netlify-identity-widget

# Auth0

cd web
yarn add @redwoodjs/auth @auth0/auth0-spa-js

# Setup

Instantiate your authentication library and pass it to the AuthProvider:

# For Netlify Identity Widget

// web/src/index.js
import { AuthProvider } from '@redwoodjs/auth'
import netlifyIdentity from 'netlify-identity-widget'


// in your JSX component
  <FatalErrorBoundary page={FatalErrorPage}>
    <AuthProvider client={netlifyIdentity} type="netlify">
        <Routes />

# For Auth0

To get your application keys, only complete the "Configure Auth0" section of the SPA Quickstart guide.

NOTE If you're using Auth0 with Redwood then you must also create an API and set the audience parameter, or you'll receive an opaque token instead of the required JWT token.

// web/src/index.js
import { AuthProvider } from '@redwoodjs/auth'
import { Auth0Client } from '@auth0/auth0-spa-js'

const auth0 = new Auth0Client({
    domain: process.env.AUTH0_DOMAIN,
    client_id: process.env.AUTH0_CLIENT_ID,
    redirect_uri: 'http://localhost:8910/',
    cacheLocation: 'localstorage',
    audience: process.env.AUTH0_AUDIENCE,

  <FatalErrorBoundary page={FatalErrorPage}>
    <AuthProvider client={auth0} type="auth0">
        <Routes />

# Usage

const UserAuthTools = () => {
  const { loading, isAuthenticated, logIn, logOut } = useAuth()

  if (loading) {
    // auth is rehydrating
    return null

  return (
      onClick={async () => {
        if (isAuthenticated) {
          await logOut()
        } else {
          await logIn()
      {isAuthenticated ? 'Log out' : 'Log in'}


The following values are available from the useAuth hook:

  • async login(): Differs based on the client library, with Netlify Identity a pop-up is shown, and with Auth0 the user is redirected
  • async logout(): Log out the current user
  • currentUser: an object containing information about the current user, or null if the user is not authenticated
  • async getToken(): returns a jwt
  • client: Access the instance of the client which you passed into AuthProvider
  • authenticated: used to determine if the current user has authenticated
  • loading: The auth state is restored asynchronously when the user visits the site for the first time, use this to determine if you have the correct state

# Usage in Redwood

Redwood provides a zeroconf experience when using our Auth package!

# GraphQL Query and Mutations

GraphQL requests automatically receive an Authorization JWT header when a user is authenticated.


If a user is signed in, the Authorization token is verified, decoded and available in context.currentUser

import { context }  from '@redwoodjs/api'

// {
//    sub: '<netlify-id>
//    email: 'user@example.com',
//    [...]
// }

You can map the "raw decoded JWT" into a real user object by passing a getCurrentUser function to createCreateGraphQLHandler

Our recommendation is to create a src/lib/auth.js|ts file that exports a getCurrentUser function (You may already have a stub function.)

import { getCurrentUser } from 'src/lib/auth'
// Example:
//  export const getCurrentUser = async (authToken: { email }) => {
//    return await db.user.findOne({ where: { email } })
//  }

export const handler = createGraphQLHandler({
  schema: makeMergedSchema({
    services: makeServices({ services }),

The value returned by getCurrentUser is available in context.currentUser

NOTE If you're using Auth0 you must also create an API and set the audience parameter, or you'll receive an opaque token instead of a JWT token, and Redwood expects to receive a JWT token.

# Routes

Routes can require authentication by wrapping them in a <Private> component. An unauthenticated user will be redirected to the page specified inunauthenticated.

import { Router, Route, Private } from "@redwoodjs/router"

  <Route path="/" page={HomePage} name="home" />
  <Route path="/login" page={LoginPage} name="login" />

  <Private unauthenticated="login">
    <Route path="/admin" page={AdminPage} name="admin" />
    <Route path="/secret-page" page={SecretPage} name="secret" />

# Contributing

Adding a new auth provider is easier than you may expect. The main objective is to map the methods of an instance of your target auth library to a shape that Redwood understands.

Here is the implementation for Auth0:

// authClients.ts
const mapAuthClientAuth0 = (client: Auth0): AuthClientAuth0 => {
  return {
    type: 'auth0',
    restoreAuthState: async () => {
      if (window.location.search.includes('code=')) {
        const { appState } = await client.handleRedirectCallback()
          appState && appState.targetUrl
            ? appState.targetUrl
            : window.location.pathname
    login: async () => client.loginWithRedirect(),
    logout: () => client.logout(),
    getToken: async () => client.getTokenSilently(),
    currentUser: async () => {
      const user = await client.getUser()
      return user || null

You'll need to import the type definition for you client and add it to the supported auth types:

// authClients.ts
export type SupportedAuthClients = Auth0 | GoTrue | NetlifyIdentity
export type SupportedAuthTypes = 'auth0' | 'gotrue' | 'netlify'