The easiest way to add authentication to your Astro project!
npm install auth-astroAuth Astro is the easiest way to add Authentication to your Astro Project. It wraps the core of Auth.js into an Astro integration, which automatically adds the endpoints and handles everything else.
#### Now supporting up to Astro 5
(disclaimer: Please don't confuse this package with astro-auth)
The easiest way to get started is adding this package using the astro cli.
``bash`
npm run astro add auth-astro
This will install the package and required peer-dependencies and add the integration to your config.
You can now jump to configuration
Alternatively, you can install the required packages on your own.
`bash`
npm install auth-astro@latest @auth/core@^0.18.6pnpm
> [!NOTE]
> If you´re using you must also install cookie: pnpm i cookie
Next, you need to add the integration to your astro config by importing it and listing it in the integrations array.
Create your auth configuration file in the root of your project.
`ts title="auth.config.ts"
// auth.config.ts
import GitHub from '@auth/core/providers/github'
import { defineConfig } from 'auth-astro'
export default defineConfig({
providers: [
GitHub({
clientId: import.meta.env.GITHUB_CLIENT_ID,
clientSecret: import.meta.env.GITHUB_CLIENT_SECRET,
}),
],
})
`
Some OAuth Providers request a callback URL be submitted alongside requesting a Client ID, and Client Secret. The callback URL used by the providers must be set to the following, unless you override the prefix field in the configuration:
`
[origin]/api/auth/callback/[provider]
// example
// http://localhost:4321/api/auth/callback/github
`
Generate an auth secret by running openssl rand -hex 32 in a local terminal or by visiting generate-secret.vercel.app, copy the string, then set it as the AUTH_SECRET environment variable describe below.
Next, set the AUTH_TRUST_HOST environment variable to true for hosting providers like Cloudflare Pages or Netlify.`sh`
AUTH_SECRET=
AUTH_TRUST_HOST=true
#### Deploying to Vercel?
Setting AUTH_TRUST_HOST is not needed, as we also check for an active Vercel environment.
- Astro config set to output mode server
- SSR enabled in your Astro projectResources:
- Enabling SSR in Your Project
- Adding an Adapter
Usage
Your authentication endpoints now live under
[origin]/api/auth/[operation]. You can change the prefix in the configuration.Accessing your configuration
In case you need to access your auth configuration, you can always import it by
`ts
import authConfig from 'auth:config'
`Sign in & Sign out
Astro Auth exposes two ways to sign in and out. Inline scripts and Astro Components.
$3
The
signIn and signOut methods can be imported dynamically in an inline script.`html
---
---
`
$3
Alternatively, you can use the
SignIn and SignOut button components provided by auth-astro/components importing them into your Astro component's script `jsx
---
import { SignIn, SignOut } from 'auth-astro/components'
---
...
...
`Fetching the session
You can fetch the session in one of two ways. The
getSession method can be used in the component script section to fetch the session.$3
`tsx title="src/pages/index.astro"
---
import { getSession } from 'auth-astro/server';const session = await getSession(Astro.request)
---
{session ? (
Welcome {session.user?.name}
) : (
Not logged in
)}
`
$3
Alternatively, you can use the
Auth component to fetch the session using a render prop.`tsx title="src/pages/index.astro"
---
import type { Session } from '@auth/core/types';
import { Auth, SignIn, SignOut } from 'auth-astro/components';
---
{(session: Session) =>
{session ?
Logout
:
Login
}
{session ?
Logged in as ${session.user?.name} : 'Not logged in'}
}
``We currently are waiting for the PR in the official next-auth repository to be merged. Once this has happened, this package will be deprecated.