Skip to main content


Built-in Google integration.


default<P>(options): OAuthConfig< P >

Add Google login to your page.


Callback URL​


import Auth from "@auth/core"
import Google from "@auth/core/providers/google"

const request = new Request(origin)
const response = await Auth(request, {
providers: [Google({ clientId: GOOGLE_CLIENT_ID, clientSecret: GOOGLE_CLIENT_SECRET })],



By default, Auth.js assumes that the Google provider is based on the Open ID Connect specification.

The "Authorized redirect URIs" used when creating the credentials must include your full domain and end in the callback path. For example;

  • For production: https://{YOUR_DOMAIN}/api/auth/callback/google
  • For development: http://localhost:3000/api/auth/callback/google

Google only provides Refresh Token to an application the first time a user signs in.

To force Google to re-issue a Refresh Token, the user needs to remove the application from their account and sign in again:

Alternatively, you can also pass options in the params object of authorization which will force the Refresh Token to always be provided on sign in, however this will ask all users to confirm if they wish to grant your application access every time they sign in.

If you need access to the RefreshToken or AccessToken for a Google account and you are not using a database to persist user accounts, this may be something you need to do.

const options = {
providers: [
clientId: process.env.GOOGLE_ID,
clientSecret: process.env.GOOGLE_SECRET,
authorization: {
params: {
prompt: "consent",
access_type: "offline",
response_type: "code"

Google also returns a email_verified boolean property in the OAuth profile.

You can use this property to restrict access to people with verified accounts at a particular domain.

const options = {
callbacks: {
async signIn({ account, profile }) {
if (account.provider === "google") {
return profile.email_verified &&"")
return true // Do different verification for other providers that don't have `email_verified`

The Google provider comes with a default configuration. To override the defaults for your use case, check out customizing a built-in OAuth provider.


If you think you found a bug in the default configuration, you can open an issue.

Auth.js strictly adheres to the specification and it cannot take responsibility for any deviation from the spec by the provider. You can open an issue, but if the problem is non-compliance with the spec, we might not pursue a resolution. You can ask for more help in Discussions.

Type parameters​

β–ͺ P extends GoogleProfile


β–ͺ options: OAuthUserConfig< P >


OAuthConfig< P >