neon-auth

작성자: neondatabase

Add authentication to a new app. Use for "add auth", "add login", Neon Auth (Managed Better Auth), identity routing, sign-up, sign-in, password reset, email OTP, magic links, organizations, phone OTP, OAuth, OAuth server for MCP or third-party OAuth clients, passkeys, MFA, trusted domains, invalid domain, and @neon/auth. No existing identity: default to Managed Better Auth. Keep working Better Auth, Clerk, Supabase Auth, or another IdP. User asked to migrate from Supabase Auth: Managed...

npx skills add https://github.com/neondatabase/agent-skills --skill neon-auth

FIRST: Use the parent neon skill for a Neon overview, getting started with Neon, Neon development best practices, and more.

If the neon skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with:

neon skills -s neon -y

Neon Auth

Neon Auth is Managed Better Auth: users, sessions, and auth config live in the neon_auth schema on the branch's Lakebase Postgres, and auth state branches with the database. The client API is the Better Auth method set (signIn.email, signIn.social, getSession) through @neon/auth. That wrapper is not a drop-in for bare better-auth/client: it pins the plugin list and adds Neon-specific OAuth verifier, iframe popup, and JWT handling. Stay on the wrapper while Auth is managed.

This skill chooses identity, then implements Managed Better Auth. It does not replace a working auth server in order to use Postgres, Functions, Object Storage, or the AI Gateway.

When to Use

Inspect existing identity and the required login features before provisioning. A supplied DATABASE_URL is not a reason to change identity. Adding a Neon Function is not a reason to change identity.

SituationWhat to do
No existing authDefault to Managed Better Auth. Managed setup, then references/managed-auth.md.
Needs a feature Managed does not offerSelf-managed Better Auth on the existing app host (Vercel or similar) or a Neon Function. Keep Lakebase Postgres. Confirm the installed Better Auth version documents that exact flow before recommending the move. If support stays unresolved, keep the current identity. references/self-managed.md.
Already has Better AuthKeep it. It works with the other Neon primitives. Migrate to Managed only if the user asks.
User asked to migrate from Supabase AuthManaged Better Auth. Supabase Auth. Moving only Postgres or adding a Function keeps Supabase Auth.
Clerk, Auth.js, Supabase Auth, or another working IdPKeep it unless the user asks to migrate.

Google, GitHub, Microsoft, Vercel, Apple, and Discord social OAuth are offered on Managed Auth. They are not a reason to leave Managed Auth. Microsoft, Apple, and Discord need your own credentials: Apple, Microsoft, and Discord OAuth. Making Neon Auth the OAuth server for your own MCP server or third-party OAuth clients is supported: references/oauth-server.md. Other OAuth providers, generic OAuth, MFA, passkeys, API keys, SSO, custom plugins, hooks, and custom JWT claims are the plugin matrix check.

Before enabling Managed Auth, confirm the project is on AWS and does not use IP Allow or Private Networking. Leave those protections in place.

Configure supported Managed plugins through Neon (Console, API, or neon neon-auth), not by passing plugins into @neon/auth. Enabling auth: true is not implementing login.

What It Does

  • Managed identity in Postgres — users and sessions in neon_auth, queryable with SQL, compatible with RLS.
  • Auth emails without an app mailer — verification, email OTP, magic links, and password reset. Getting started uses shared SMTP (auth@mail.myneon.app). You do not add Resend or SendGrid to implement login. Production needs custom SMTP: https://neon.com/docs/auth/production-checklist.md
  • Branches with the database — each branch has its own Auth URL and isolated auth state.
  • Better Auth client methods via the Neon SDK — @neon/auth (auth only) or @neon/neon-js/auth (combined SDK). Optional UI: Better Auth UI (@better-auth-ui/react with its shadcn/ui components).
  • Fixed plugin set — the Managed client does not accept a plugins option. See plugin support.

Availability

Managed Better Auth is generally available. AWS regions only. It cannot be enabled on a project with IP Allow or Private Networking.

Organization is separately Partial / Beta. Hosting self-managed Better Auth in a Neon Function follows Functions availability and claim rules; use the neon-functions skill for that host. An unclaimed project that can enable Auth still cannot use Functions until claim.

Managed setup

Merge Auth into the existing neon.ts. Do not replace other fields:

import { defineConfig } from "@neon/config/v1";

export default defineConfig({
  auth: true,
});
neon deploy
neon neon-auth status

If Function env in that config reads process.env, use neon deploy --env <file> as the parent skill describes. The manual service command is neon neon-auth enable; do not run both enable and deploy as redundant required steps when neon.ts already declares auth: true.

Then implement login: references/managed-auth.md. To make Neon Auth the OAuth server for an MCP server or OAuth clients, continue to references/oauth-server.md.

Claimable projects: follow the parent Claimable path, then auth: true and neon deploy when login is requested and no existing provider should be preserved.

Supabase Auth

When the user asked to migrate login from Supabase Auth, recommend Managed Better Auth and follow https://neon.com/docs/auth/migrate/from-supabase.md. Moving only Postgres or adding a Function is not that request: keep Supabase Auth.

SupabaseAuthAdapter() keeps method shapes such as signInWithPassword and signInWithOAuth. Those calls are not interchangeable with default Better Auth examples (signIn.email). Keep an existing adapter caller on that API.

Inventory the auth methods and database calls actually used:

  • Password hashes cannot transfer. Users create new accounts or sign in with OAuth.
  • Do not promise unchanged user IDs, sessions, or account linking. Plan application foreign keys with the owner.
  • updateUser() cannot change email or password on Managed Auth. Email verification needs application UI (codes work on shared SMTP; links need custom SMTP).
  • The migration guide lists Supabase phone/SMS/WhatsApp, SAML, and Web3 as unsupported on Managed Auth. Confirm the installed Better Auth version if the user still needs that exact flow; if support stays unresolved, keep Supabase Auth and stop the auth cutover. That page's "no phone auth" claim is about Supabase phone sign-in, not the constrained Managed Phone Number plugin (existing users link a number).
  • @supabase/supabase-js used only for Auth does not justify enabling the Data API. Keep Data API only for existing PostgREST / Supabase database-client queries.

Verification

Managed path: sign-up, sign-in, sign-out, session restoration after reload, and protected access, including error and loading states. Exercise email verification (code on shared SMTP) when it is on. Report any flow that remains unverified.

A required plugin on the self-managed path is verified in that app's Better Auth setup, not as a Managed flow.

Plugin support

Checked 2026-10-30 against https://neon.com/docs/auth/guides/plugins.md, https://neon.com/docs/auth/guides/plugins/oauth-provider.md, https://neon.com/docs/auth/roadmap.md, and the @neon/auth client plugin list. Discord row checked 2026-11-11 against https://neon.com/docs/reference/api/auth/add-branch-neon-auth-oauth-provider.md; Discord: see Apple, Microsoft, and Discord OAuth. Re-fetch those pages if this skill may be stale. An unlisted upstream plugin needs a live check; do not treat absence from this table as a dated roadmap item.

"Not exposed" means the Managed SDK/UI contract. It is not a claim that every raw server request was tested.

FeatureManaged AuthBoundary
Email/passwordSupportedsignUp.email, signIn.email
Social OAuth (Google, GitHub, Microsoft, Vercel, Apple, Discord)SupportedsignIn.social. Shared Google credentials are for development; production and GitHub/Vercel need your own OAuth apps. Microsoft, Apple, and Discord always need your own. Discord: see details. https://neon.com/docs/auth/guides/setup-oauth.md
AdminSupportedAdmin session required. Plugin customization is on the roadmap.
Email OTPSupportedManaged delivery. emailOtp.sendVerificationOtp, signIn.emailOtp.
Magic LinkSupportedEnable on the branch (off by default). signIn.magicLink.
OrganizationPartial, BetaMembers, invitations, owner/admin/member. No Teams, server hooks, custom roles/permissions, or dynamic access control. Emailed invitations: managed-auth.md.
JWTSupportedEdDSA (Ed25519), 15-minute expiry, no custom claims. Default client: .token() then data.token. SupabaseAuthAdapter(): getSession() then data.session.access_token (no .token()).
Open APISupportedServer routes /reference and /open-api/generate-schema.
Phone NumberSupported with constraintsBrowser client: existing users link a number, then sign in; no phone-first signup; own SMS webhook; custom UI. Next.js auth.handler() forwards the catch-all path, including phone OTP. A missing auth.phoneNumber server method is a missing typed helper, not a proxy rejection. https://neon.com/docs/auth/guides/plugins/phone-number.md
MFA / Two-FactorRoadmapUnavailable on Managed Auth. If required: self-managed.md, after confirming the installed Better Auth version.
Passkey, API Key, Generic OAuth, One Tap, Multi SessionNot exposed by Managed SDK/UIIf required: self-managed.md. Generic OAuth is not Google/GitHub/Microsoft/Vercel/Apple/Discord social sign-in.
OAuth Provider (OAuth server, MCP auth)Supported (beta)Neon Auth is the OAuth 2.1 / OIDC server for your MCP server or third-party OAuth clients. You host the login and consent pages; no client credentials grant. See references/oauth-server.md.
SSO / SAMLNot listed or exposedIf required: self-managed.md, after confirming the installed Better Auth version.

The default Managed client method is getAnonymousToken(). That JWT is a Neon anonymous Data API token. It is not Better Auth's Anonymous-account plugin (signIn.anonymous). anonymousTokenClient() is the SDK plugin factory, not a method on the public client. Do not call it, and do not call getAnonymousToken() on SupabaseAuthAdapter().

Trusted domains and webhooks are Neon settings, not installable Better Auth plugins.

Apple, Microsoft, and Discord OAuth

Apple, Microsoft, and Discord reject shared credentials. Add them with your own via neon neon-auth oauth-provider add|update (Console and API work too). A multi-line secret goes in a file with --oauth-client-secret-file, not inline.

  • Apple: client_id is the Services ID, client_secret is the full .p8 private key. Also pass --apple-team-id and --apple-key-id (10 characters). Neon Auth signs the client-secret JWT itself, so there is nothing to rotate. Rotating the key needs the new --apple-key-id in the same update. The return URL must be HTTPS (https://<auth host>/<db>/auth/callback/apple); Apple rejects localhost, so test through a tunnel or a deployed preview.
  • Microsoft: client_id and client_secret from the Entra app registration. --microsoft-tenant-id is optional: common (default), organizations, consumers, a tenant GUID, or a domain. The redirect URI is <base_url>/callback/microsoft.
  • Microsoft email verification: an email counts as verified only when the ID token carries xms_edov = true and acct = 0. Add xms_edov and acct as optional ID-token claims in Entra. Without them, a same-email existing user gets account_not_linked, link-social fails with unable_to_link_account, and new users stay unverified.
  • Discord: Always needs your own Discord application client_id and client_secret (shared is rejected on add and update). Better Auth only; legacy Stack Auth returns 422. Scopes are identify and email. Redirect URI <base_url>/callback/discord. With Neon CLI 9.5.0 or later, add or update it like Microsoft using --provider-id discord, --oauth-client-id, and --oauth-client-secret-file (preferred to keep the secret out of shell history). Delete it with neon neon-auth oauth-provider delete --provider-id discord. Older CLIs can use MCP auth.oauthProviders.add|update|delete or the API: https://neon.com/docs/reference/api/auth/add-branch-neon-auth-oauth-provider.md
  • Discord email verification: an email counts as verified only when Discord's verified is the boolean true. An unverified Discord email cannot auto-link to an existing same-email user, and a new user from it is stored as unverified. A Discord account with no email fails with email_not_found.

Trusted domains

Auth redirects only to origins on its allowlist. invalid domain means the app origin is missing. Include the scheme, omit a trailing slash, register production and preview origins before pointing users at them, and target the correct branch:

neon neon-auth domain add https://app.example.com
neon neon-auth domain list
neon neon-auth domain delete https://old.example.com

Localhost ports are pre-approved by default. An existing project can have that off: neon neon-auth domain allow-localhost get|enable|disable. Docs: https://neon.com/docs/auth/guides/configure-domains.md

OAuth provider redirect is {NEON_AUTH_BASE_URL}/callback/{provider} (the Auth URL includes its path). callbackURL on signIn.social is the later app landing origin and must be trusted.

The Managed SDK handles iframe OAuth popup and neon_auth_session_verifier. Keep the wrapper, callback route, and middleware. Do not reimplement that flow, and do not promise third-party cookies in every browser.

Functions and Data API

A Function authenticates whoever already signs the user in. Do not switch identity to call a Function. Verify the token in the neon-functions skill and https://neon.com/docs/compute/functions/authentication.md.

Managed Auth: injected NEON_AUTH_JWKS_URL, issuer from NEON_AUTH_BASE_URL. Token: default client .token() then data.token; SupabaseAuthAdapter() getSession() then data.session.access_token. A valid token is not permission to read another user's rows. Sign-out ends the browser session; do not claim it immediately revokes an already-issued JWT.

Data API identity: references/managed-auth.md. New apps query Postgres from Functions or existing handlers, not the Data API.

neondatabase의 다른 스킬

add-neon-docs
neondatabase
사용자가 Neon에 대한 문서 추가, 문서 추가, 참조 추가, 또는 문서 설치를 요청할 때 이 스킬을 사용하세요. Neon 모범 사례 참조 링크를 추가합니다…
better-env
neondatabase
에이전트와 인간을 위한 더 나은 환경 변수 관리로, 완전한 타입 안전성, CLI 기반 원격 환경 동기화, 환경 검증을 제공합니다.…
claimable-postgres
neondatabase
로컬 개발, 데모, 프로토타이핑 및 테스트 환경을 위한 즉시 사용 가능한 Postgres 데이터베이스입니다. 계정이 필요하지 않습니다. 데이터베이스는 Neon 계정에 클레임되지 않으면 72시간 후에 만료됩니다.
claimable-postgres
neondatabase
Neon의 Claimable Postgres(pg.new)로 즉시 Postgres 데이터베이스를 생성하여 빠른 로컬 개발, 데모, 프로토타이핑 및 테스트 환경에 사용하세요.
logging-best-practices
neondatabase
강력한 디버깅과 분석을 위한 광범위한 이벤트(표준 로그 라인)에 초점을 맞춘 로깅 모범 사례
neon
neondatabase
Neon 플랫폼 개요: Postgres, Auth, Data API, 그리고 새로운 서비스인 Object Storage, Compute Functions, AI Gateway를 포함한 앱 및 에이전트 지원. "Neon"이 언급될 때마다 Neon 사용 방법과 시작 가이드 개요로 활용. 개별 기능은 다음 트리거로 연결: "object storage" 또는 "S3-compatible storage", "serverless functions", "background jobs", 또는 "run code near my database", "AI gateway", "LLM proxy", "model routing", 또는 "call an LLM" →...
apidevelopmentdatabase
neon-ai-gateway
neondatabase
프론티어 및 오픈소스 LLM을 위한 하나의 API와 하나의 자격 증명으로, Neon 브랜치에 내장되어 Databricks에서 구동됩니다. 사용자가 LLM을 호출하거나 추가하려는 경우 사용하세요.
neon-auth
neondatabase
애플리케이션에 Neon Auth를 설정합니다. 인증을 구성하고, 인증 라우트를 생성하며, UI 컴포넌트를 생성합니다. Next.js에 인증을 추가할 때 사용합니다.