Set up OAuth

OAuth lets users sign in with their Google, GitHub, or Vercel account. Neon Auth handles the OAuth flow and creates a session after authorization.

Development mode

Google OAuth is enabled by default with shared credentials for development and testing. You can start using Google sign-in immediately without any configuration.

For production, configure your own OAuth app credentials for both providers. See Production setup below.

Sign in with OAuth

Call signIn.social() with your provider ("google", "github" or "vercel"). The SDK redirects the user to the provider's authorization page, then back to your callbackURL:

import { authClient } from './auth';

const handleGoogleSignIn = async () => {
  try {
    await authClient.signIn.social({
      provider: "google",
      callbackURL: window.location.origin,
    });
  } catch (error) {
    console.error("Google sign-in error:", error);
  }
};

Handle the callback

After the provider redirects back to your app, check for a session:

import { authClient } from './auth';

useEffect(() => {
  authClient.getSession().then(({ data }) => {
    if (data?.session) {
      setUser(data.session.user);
    }
    setLoading(false);
  });
}, []);

Custom redirect URLs

Specify different URLs for new users or errors:

await authClient.signIn.social({
  provider: "google", // or "github", "vercel"
  callbackURL: "/dashboard",
  newUserCallbackURL: "/welcome",
  errorCallbackURL: "/error",
});

Production setup

For production, configure your own OAuth app credentials. GitHub and Vercel OAuth require custom credentials, while Google OAuth works with shared credentials for development but should use custom credentials in production.

1. Create OAuth apps with your providers:
   • Google OAuth setup (see Google OAuth branding below before going live)
   • GitHub OAuth setup
   • Vercel OAuth setup
2. In your project's Settings → Auth page, configure your Client ID and Client Secret for each provider

Your app will automatically use your configured credentials

Google OAuth branding

When using your own Google OAuth credentials, users will see a consent screen before signing in. Without branding configured, Google displays the redirect_uri domain ("Continue to neon.tech") instead of your app's name. This happens even when your OAuth client ID and secret are correctly configured.

To show your app's name on the consent screen:

1. Go to Google Cloud Console → OAuth consent screen
2. Fill in the required app information:
   • App name: the name users will see on the consent screen
   • User support email: a contact email for users with auth questions
   • Developer contact information: your email address (not shown to users)
3. Under Authorized domains, add your app's domain (for example, myapp.com)
4. Save your changes

• 

  Email Verification

  Add email verification