Auth0 Integration

Use Auth0 when the identity provider should host login and enterprise connections while Farm owns the application-facing OAuth routes and local session.

The built-in flow uses Authorization Code with PKCE, validates signed state, reads the user profile, and stores that profile in a signed HTTP-only cookie.

Add Auth0

farm add integration auth0 --ui

Configure

import { auth0 } from "@farm.js/integrations/auth0";export const appIntegrations = {  auth: auth0({    domain: process.env.AUTH0_DOMAIN,    clientId: process.env.AUTH0_CLIENT_ID,    clientSecret: process.env.AUTH0_CLIENT_SECRET,    secret: process.env.AUTH0_SECRET,    appBaseUrl: process.env.APP_BASE_URL,    callbackPath: "/auth/callback",    protectedRoutes: ["/dashboard(.*)"],  }),} as const;export type AppIntegrations = typeof appIntegrations;

callbackPath stays root-relative. Farm combines it with APP_BASE_URL, or the incoming request origin, to create the callback URL sent to Auth0.

You can use callbackUrl instead, but it must be absolute:

auth0({  callbackUrl: "https://app.example.com/auth/callback",});

Choose route ownership

Let Farm construct the Auth0 flow

The configuration above is the default path. When instance is omitted, Farm constructs the OAuth flow from the Auth0 domain, client credentials, session secret, callback settings, and scopes. Farm then owns the login, signup, callback, logout, profile, and protected-route behavior.

Provide application-owned middleware

auth0({  instance: {    matcher: ["/auth(.*)", "/dashboard(.*)"],    middleware(request) {      return myAuth0Middleware(request);    },  },});

This advanced path accepts a compatible middleware adapter rather than the Auth0 SDK itself. The supplied instance wins and Farm only mounts its middleware; it does not create the built-in login, callback, logout, or profile routes.

Environment variables

Farm provides a development-only fallback for AUTH0_SECRET. Production startup fails when no secret is configured.

Routes and methods

Every path can be changed with loginPath, signUpPath, callbackPath, logoutPath, or profilePath.

Start login

Normal document navigation redirects directly:

<a href="/auth/login?returnTo=/dashboard">Sign in</a>

The typed integration client asks for the redirect URL as JSON:

const result = await apiClient.auth.login.get({  query: {    returnTo: "/dashboard",  },});if (result.data) {  window.location.assign(result.data.redirectTo);}

Signup uses the same shape through apiClient.auth.signup.get(...).

Read the profile

const result = await api.auth.profile.get();if (result.error && "status" in result.error && result.error.status === 401) {  // No valid local Auth0 session.}const user = result.data?.user;

The session cookie contains the fetched Auth0 profile and an expiry derived from the token response. The integration does not persist refresh tokens, so an expired local session requires a new login.

Protect app routes

auth0({  protectedRoutes: ["/dashboard(.*)", "/settings(.*)"],});

A signed-out request is redirected with status 307 to:

/auth/login?returnTo=/the/original/path

Only root-relative returnTo values are accepted. Invalid or external values fall back to /dashboard.

Options

Production checklist

• Allow the exact callback URL in Auth0.
• Allow the app origin as a logout URL.
• Use a strong AUTH0_SECRET.
• Set APP_BASE_URL behind proxies or custom domains.
• Test bad state, callback errors, expired cookies, login return paths, and logout.