You will use a password when you ____

Notifications

Table of Contents Show

Before you begin
Handle the sign-in flow with the Firebase SDK
Redirect mode
Authenticate with Firebase in a Chrome extension

Save this page to your Developer Profile to get notifications on important updates.

Stay organized with collections

Save and categorize content based on your preferences.

You can let your users authenticate with Firebase using their Google Accounts. You can either use the Firebase SDK to carry out the Google sign-in flow, or carry out the sign-in flow manually using the Sign In With Google library and passing the resulting ID token to Firebase.

Before you begin

If you are building a web app, the easiest way to authenticate your users with Firebase using their Google Accounts is to handle the sign-in flow with the Firebase JavaScript SDK. (If you want to authenticate a user in Node.js or other non-browser environment, you must handle the sign-in flow manually.)

To handle the sign-in flow with the Firebase JavaScript SDK, follow these steps:

Create an instance of the Google provider object:

Learn more about the tree-shakeable Web v9 modular SDK and upgrade from version 8. import { GoogleAuthProvider } from "firebase/auth"; const provider = new GoogleAuthProvider();

var provider = new firebase.auth.GoogleAuthProvider();
Optional: Specify additional OAuth 2.0 scopes that you want to request from the authentication provider. To add a scope, call addScope. For example:

Learn more about the tree-shakeable Web v9 modular SDK and upgrade from version 8. provider.addScope('https://www.googleapis.com/auth/contacts.readonly');

provider.addScope('https://www.googleapis.com/auth/contacts.readonly');

See the authentication provider documentation.
Optional: To localize the provider's OAuth flow to the user's preferred language without explicitly passing the relevant custom OAuth parameters, update the language code on the Auth instance before starting the OAuth flow. For example:

Learn more about the tree-shakeable Web v9 modular SDK and upgrade from version 8. import { getAuth } from "firebase/auth"; const auth = getAuth(); auth.languageCode = 'it'; // To apply the default browser preference instead of explicitly setting it. // firebase.auth().useDeviceLanguage();

firebase.auth().languageCode = 'it'; // To apply the default browser preference instead of explicitly setting it. // firebase.auth().useDeviceLanguage();
Optional: Specify additional custom OAuth provider parameters that you want to send with the OAuth request. To add a custom parameter, call setCustomParameters on the initialized provider with an object containing the key as specified by the OAuth provider documentation and the corresponding value. For example:

Learn more about the tree-shakeable Web v9 modular SDK and upgrade from version 8. provider.setCustomParameters({ 'login_hint': '' });

provider.setCustomParameters({ 'login_hint': '' });

Reserved required OAuth parameters are not allowed and will be ignored. See the authentication provider reference for more details.
Authenticate with Firebase using the Google provider object. You can prompt your users to sign in with their Google Accounts either by opening a pop-up window or by redirecting to the sign-in page. The redirect method is preferred on mobile devices.
- To sign in with a pop-up window, call signInWithPopup:
  
  Learn more about the tree-shakeable Web v9 modular SDK and upgrade from version 8. import { getAuth, signInWithPopup, GoogleAuthProvider } from "firebase/auth"; const auth = getAuth(); signInWithPopup(auth, provider) .then((result) => { // This gives you a Google Access Token. You can use it to access the Google API. const credential = GoogleAuthProvider.credentialFromResult(result); const token = credential.accessToken; // The signed-in user info. const user = result.user; // ... }).catch((error) => { // Handle Errors here. const errorCode = error.code; const errorMessage = error.message; // The email of the user's account used. const email = error.customData.email; // The AuthCredential type that was used. const credential = GoogleAuthProvider.credentialFromError(error); // ... });
  
  firebase.auth() .signInWithPopup(provider) .then((result) => { /** @type {firebase.auth.OAuthCredential} */ var credential = result.credential; // This gives you a Google Access Token. You can use it to access the Google API. var token = credential.accessToken; // The signed-in user info. var user = result.user; // ... }).catch((error) => { // Handle Errors here. var errorCode = error.code; var errorMessage = error.message; // The email of the user's account used. var email = error.email; // The firebase.auth.AuthCredential type that was used. var credential = error.credential; // ... });
  
  Also notice that you can retrieve the Google provider's OAuth token which can be used to fetch additional data using the Google APIs.
  This is also where you can catch and handle errors. For a list of error codes have a look at the Auth Reference Docs.
- To sign in by redirecting to the sign-in page, call signInWithRedirect:
  
  Learn more about the tree-shakeable Web v9 modular SDK and upgrade from version 8. import { getAuth, signInWithRedirect } from "firebase/auth"; const auth = getAuth(); signInWithRedirect(auth, provider);
  
  firebase.auth().signInWithRedirect(provider);
  
  Then, you can also retrieve the Google provider's OAuth token by calling getRedirectResult when your page loads:
  
  Learn more about the tree-shakeable Web v9 modular SDK and upgrade from version 8. import { getAuth, getRedirectResult, GoogleAuthProvider } from "firebase/auth"; const auth = getAuth(); getRedirectResult(auth) .then((result) => { // This gives you a Google Access Token. You can use it to access Google APIs. const credential = GoogleAuthProvider.credentialFromResult(result); const token = credential.accessToken; // The signed-in user info. const user = result.user; }).catch((error) => { // Handle Errors here. const errorCode = error.code; const errorMessage = error.message; // The email of the user's account used. const email = error.customData.email; // The AuthCredential type that was used. const credential = GoogleAuthProvider.credentialFromError(error); // ... });
  
  firebase.auth() .getRedirectResult() .then((result) => { if (result.credential) { /** @type {firebase.auth.OAuthCredential} */ var credential = result.credential; // This gives you a Google Access Token. You can use it to access the Google API. var token = credential.accessToken; // ... } // The signed-in user info. var user = result.user; }).catch((error) => { // Handle Errors here. var errorCode = error.code; var errorMessage = error.message; // The email of the user's account used. var email = error.email; // The firebase.auth.AuthCredential type that was used. var credential = error.credential; // ... });
  
  This is also where you can catch and handle errors. For a list of error codes have a look at the Auth Reference Docs.

Google serves as both an email and social identity provider. Email IDPs are authoritative for all email addresses related to their hosted email domain while social IDPs assert email identities based having done a one time confirmation of the email address. A user logging in with Google will never cause this error when their account is hosted at Google even if they signed up for their account with a password or a social IDP.

If you enabled the One account per email address setting in the Firebase console, when a user tries to sign in a to a provider (such as Google) with an email that already exists for another Firebase user's provider (such as Facebook), the error auth/account-exists-with-different-credential is thrown along with an AuthCredential object (Google ID token). To complete the sign in to the intended provider, the user has to sign first to the existing provider (Facebook) and then link to the former AuthCredential (Google ID token).

If you use signInWithPopup, you can handle auth/account-exists-with-different-credential errors with code like the following example:

// Step 1. // User tries to sign in to Google. auth.signInWithPopup(new firebase.auth.GoogleAuthProvider()).catch(function(error) { // An error happened. if (error.code === 'auth/account-exists-with-different-credential') { // Step 2. // User's email already exists. // The pending Google credential. var pendingCred = error.credential; // The provider account's email address. var email = error.email; // Get sign-in methods for this email. auth.fetchSignInMethodsForEmail(email).then(function(methods) { // Step 3. // If the user has several sign-in methods, // the first method in the list will be the "recommended" method to use. if (methods[0] === 'password') { // Asks the user their password. // In real scenario, you should handle this asynchronously. var password = promptUserForPassword(); // TODO: implement promptUserForPassword. auth.signInWithEmailAndPassword(email, password).then(function(result) { // Step 4a. return result.user.linkWithCredential(pendingCred); }).then(function() { // Google account successfully linked to the existing Firebase user. goToApp(); }); return; } // All the other cases are external providers. // Construct provider object for that provider. // TODO: implement getProviderForProviderId. var provider = getProviderForProviderId(methods[0]); // At this point, you should let the user know that they already have an account // but with a different provider, and let them validate the fact they want to // sign in with this provider. // Sign in to provider. Note: browsers usually block popup triggered asynchronously, // so in real scenario you should ask the user to click on a "continue" button // that will trigger the signInWithPopup. auth.signInWithPopup(provider).then(function(result) { // Remember that the user may have signed in with an account that has a different email // address than the first one. This can happen as Firebase doesn't control the provider's // sign in flow and the user is free to login using whichever account they own. // Step 4b. // Link to Google credential. // As we have access to the pending credential, we can directly call the link method. result.user.linkAndRetrieveDataWithCredential(pendingCred).then(function(usercred) { // Google account successfully linked to the existing Firebase user. goToApp(); }); }); }); } });

Redirect mode

This error is handled in a similar way in the redirect mode, with the difference that the pending credential has to be cached between page redirects (for example, using session storage).

You can also authenticate with Firebase using a Google Account by handling the sign-in flow with the Sign In With Google library:

Integrate Sign In With Google into your app by following the integration guide. Be sure to configure Google Sign-In with the Google Client ID generated for your Firebase project. You can find your project's Google Client ID in your Project's Developers Console Credentials page.
In the sign-in result callback, exchange the ID token from the Google auth response for a Firebase credential and use it to authenticate with Firebase: function handleCredentialResponse(response) { // Build Firebase credential with the Google ID token. const idToken = response.credential; const credential = GoogleAuthProvider.credential(idToken); // Sign in with credential from the Google user. signInWithCredential(auth, credential).catch((error) => { // Handle Errors here. const errorCode = error.code; const errorMessage = error.message; // The email of the user's account used. const email = error.email; // The credential that was used. const credential = GoogleAuthProvider.credentialFromError(error); // ... }); }

To authenticate with Firebase in a Node.js application:

Sign in the user with their Google Account and get the user's Google ID token. You can accomplish this in several ways. For example:
- If your app has a browser front end, use Google Sign-In as described in the Handle the sign-in flow manually section. Get the Google ID token from the auth response: var id_token = googleUser.getAuthResponse().id_token Then, send this token to your Node.js app.
- If your app runs on a device with limited input capabilities, such as a TV, you can use the Google Sign-In for TVs and Devices flow.
After you get the user's Google ID token, use it to build a Credential object and then sign in the user with the credential:

Learn more about the tree-shakeable Web v9 modular SDK and upgrade from version 8. import { getAuth, signInWithCredential, GoogleAuthProvider } from "firebase/auth"; // Build Firebase credential with the Google ID token. const credential = GoogleAuthProvider.credential(id_token); // Sign in with credential from the Google user. const auth = getAuth(); signInWithCredential(auth, credential).catch((error) => { // Handle Errors here. const errorCode = error.code; const errorMessage = error.message; // The email of the user's account used. const email = error.customData.email; // The AuthCredential type that was used. const credential = GoogleAuthProvider.credentialFromError(error); // ... });

// Build Firebase credential with the Google ID token. var credential = firebase.auth.GoogleAuthProvider.credential(id_token); // Sign in with credential from the Google user. firebase.auth().signInWithCredential(credential).catch((error) => { // Handle Errors here. var errorCode = error.code; var errorMessage = error.message; // The email of the user's account used. var email = error.email; // The firebase.auth.AuthCredential type that was used. var credential = error.credential; // ... });

Authenticate with Firebase in a Chrome extension

If you are building a Chrome extension app, you must add your Chrome extension ID:

Open your project in the Firebase console.
In the Authentication section, open the Sign-in method page.
Add a URI like the following to the list of Authorized Domains: chrome-extension://CHROME_EXTENSION_ID

Only popup operations (signInWithPopup, linkWithPopup, and reauthenticateWithPopup) are available to Chrome extensions, as Chrome extensions cannot use HTTP redirects. You should call these methods from a background page script rather than a browser action popup, as the authentication popup will cancel the browser action popup. The popup methods may only be used in extensions using Manifest V2. The newer Manifest V3 only allows background scripts in the form of service workers, which cannot perform the popup operations at all.

In your Chrome extension's manifest file make sure that you add the https://apis.google.com URL to the content_security_policy allowlist.

On project creation, Firebase will provision a unique subdomain for your project: https://my-app-12345.firebaseapp.com.

This will also be used as the redirect mechanism for OAuth sign in. That domain would need to be allowed for all supported OAuth providers. However, this means that users may see that domain while signing in to Google before redirecting back to the application: Continue to: https://my-app-12345.firebaseapp.com.

To avoid displaying your subdomain, you can set up a custom domain with Firebase Hosting:

Follow steps 1 through 3 in Set up your domain for Hosting. When you verify your domain ownership, Hosting provisions an SSL certificate for your custom domain.
Add your custom domain to the list of authorized domains in the Firebase console: auth.custom.domain.com.
In the Google developer console or OAuth setup page, whitelist the URL of the redirect page, which will be accessible on your custom domain: https://auth.custom.domain.com/__/auth/handler.
When you initialize the JavaScript library, specify your custom domain with the authDomain field: var config = { apiKey: '...', // Changed from 'my-app-12345.firebaseapp.com'. authDomain: 'auth.custom.domain.com', databaseURL: 'https://my-app-12345.firebaseio.com', projectId: 'my-app-12345', storageBucket: 'my-app-12345.appspot.com', messagingSenderId: '1234567890' }; firebase.initializeApp(config);

Next steps

After a user signs in for the first time, a new user account is created and linked to the credentials—that is, the user name and password, phone number, or auth provider information—the user signed in with. This new account is stored as part of your Firebase project, and can be used to identify a user across every app in your project, regardless of how the user signs in.

In your apps, the recommended way to know the auth status of your user is to set an observer on the Auth object. You can then get the user's basic profile information from the User object. See Manage Users.
In your Firebase Realtime Database and Cloud Storage Security Rules, you can get the signed-in user's unique user ID from the auth variable, and use it to control what data a user can access.

You can allow users to sign in to your app using multiple authentication providers by linking auth provider credentials to an existing user account.

To sign out a user, call signOut:

Learn more about the tree-shakeable Web v9 modular SDK and upgrade from version 8. import { getAuth, signOut } from "firebase/auth"; const auth = getAuth(); signOut(auth).then(() => { // Sign-out successful. }).catch((error) => { // An error happened. });

firebase.auth().signOut().then(() => { // Sign-out successful. }).catch((error) => { // An error happened. });