Stay organized with collectionsSave and categorize content based on your preferences.
You can let your users authenticate with Firebase using their Twitter accounts
by integrating Twitter authentication into your app. You can integrate Twitter
authentication either by using the Firebase SDK to carry out the sign-in flow,
or by carrying out the Twitter OAuth flow manually and passing the resulting
access token and secret to Firebase.
On theSign in methodtab, enable theTwitterprovider.
Add theAPI keyandAPI secretfrom that provider's developer console to the
provider configuration:
Register your appas a developer application on Twitter and get your app's OAuthAPI keyandAPI secret.
Make sure your FirebaseOAuth redirect URI(e.g.my-app-12345.firebaseapp.com/__/auth/handler)
is set as yourAuthorization callback URLin your app's settings page on yourTwitter app's config.
ClickSave.
Handle the sign-in flow with the Firebase SDK
If you are building a web app, the easiest way to authenticate your users
with Firebase using their Twitter 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 Twitter provider object:
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:
Web
import{getAuth}from"firebase/auth";constauth=getAuth();auth.languageCode='it';// To apply the default browser preference instead of explicitly setting it.// auth.useDeviceLanguage();
Optional: Specify additional custom OAuth provider parameters
that you want to send with the OAuth request. To add a custom parameter, callsetCustomParameterson the initialized provider with an object containing the key
as specified by the OAuth provider documentation and the corresponding value. For example:
Authenticate with Firebase using the Twitter provider object. You can
prompt your users to sign in with their Twitter 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, callsignInWithPopup:
Web
import{getAuth,signInWithPopup,TwitterAuthProvider}from"firebase/auth";constauth=getAuth();signInWithPopup(auth,provider).then((result)=>{// This gives you a the Twitter OAuth 1.0 Access Token and Secret.// You can use these server side with your app's credentials to access the Twitter API.constcredential=TwitterAuthProvider.credentialFromResult(result);consttoken=credential.accessToken;constsecret=credential.secret;// The signed-in user info.constuser=result.user;// IdP data available using getAdditionalUserInfo(result)// ...}).catch((error)=>{// Handle Errors here.consterrorCode=error.code;consterrorMessage=error.message;// The email of the user's account used.constemail=error.customData.email;// The AuthCredential type that was used.constcredential=TwitterAuthProvider.credentialFromError(error);// ...});
firebase.auth().signInWithPopup(provider).then((result)=>{/** @type {firebase.auth.OAuthCredential} */varcredential=result.credential;// This gives you a the Twitter OAuth 1.0 Access Token and Secret.// You can use these server side with your app's credentials to access the Twitter API.vartoken=credential.accessToken;varsecret=credential.secret;// The signed-in user info.varuser=result.user;// IdP data available in result.additionalUserInfo.profile.// ...}).catch((error)=>{// Handle Errors here.varerrorCode=error.code;varerrorMessage=error.message;// The email of the user's account used.varemail=error.email;// The firebase.auth.AuthCredential type that was used.varcredential=error.credential;// ...});
Then, you can also retrieve the Twitter provider's OAuth token by callinggetRedirectResultwhen your page loads:
Web
import{getAuth,getRedirectResult,TwitterAuthProvider}from"firebase/auth";constauth=getAuth();getRedirectResult(auth).then((result)=>{// This gives you a the Twitter OAuth 1.0 Access Token and Secret.// You can use these server side with your app's credentials to access the Twitter API.constcredential=TwitterAuthProvider.credentialFromResult(result);consttoken=credential.accessToken;constsecret=credential.secret;// ...// The signed-in user info.constuser=result.user;// IdP data available using getAdditionalUserInfo(result)// ...}).catch((error)=>{// Handle Errors here.consterrorCode=error.code;consterrorMessage=error.message;// The email of the user's account used.constemail=error.customData.email;// The AuthCredential type that was used.constcredential=TwitterAuthProvider.credentialFromError(error);// ...});
firebase.auth().getRedirectResult().then((result)=>{if(result.credential){/** @type {firebase.auth.OAuthCredential} */varcredential=result.credential;// This gives you a the Twitter OAuth 1.0 Access Token and Secret.// You can use these server side with your app's credentials to access the Twitter API.vartoken=credential.accessToken;varsecret=credential.secret;// ...}// The signed-in user info.varuser=result.user;// IdP data available in result.additionalUserInfo.profile.// ...}).catch((error)=>{// Handle Errors here.varerrorCode=error.code;varerrorMessage=error.message;// The email of the user's account used.varemail=error.email;// The firebase.auth.AuthCredential type that was used.varcredential=error.credential;// ...});
If you enabled theOne account per email addresssetting in theFirebaseconsole,
when a user tries to sign in a to a provider (such as Twitter) with an email that already
exists for another Firebase user's provider (such as Google), the errorauth/account-exists-with-different-credentialis thrown along with anAuthCredentialobject (Twitter oauth token and secret). To complete the sign in to the
intended provider, the user has to sign first to the existing provider (Google) and then link to the
formerAuthCredential(Twitter oauth token and secret).
Popup mode
If you usesignInWithPopup, you can handleauth/account-exists-with-different-credentialerrors with code like the following
example:
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).
Handle the sign-in flow manually
You can also authenticate with Firebase using a Twitter account by handling the
sign-in flow by calling the Twitter OAuth endpoints:
Integrate Twitter authentication into your app by following thedeveloper's documentation. At the end of the Twitter sign-in flow, you
will receive an OAuth access token and an OAuth secret.
If you need to sign in on a Node.js application, send the OAuth access
token and the OAuth secret to the Node.js application.
After a user successfully signs in with Twitter, exchange the OAuth access
token and OAuth secret for a Firebase credential:
Authenticate with Firebase using the Firebase credential:
Web
import{getAuth,signInWithCredential,FacebookAuthProvider}from"firebase/auth";// Sign in with the credential from the Facebook user.constauth=getAuth();signInWithCredential(auth,credential).then((result)=>{// Signed inconstcredential=FacebookAuthProvider.credentialFromResult(result);}).catch((error)=>{// Handle Errors here.consterrorCode=error.code;consterrorMessage=error.message;// The email of the user's account used.constemail=error.customData.email;// The AuthCredential type that was used.constcredential=FacebookAuthProvider.credentialFromError(error);// ...});
// Sign in with the credential from the Facebook user.firebase.auth().signInWithCredential(credential).then((result)=>{// Signed invarcredential=result.credential;// ...}).catch((error)=>{// Handle Errors here.varerrorCode=error.code;varerrorMessage=error.message;// The email of the user's account used.varemail=error.email;// The firebase.auth.AuthCredential type that was used.varcredential=error.credential;// ...});
Customizing the redirect domain for Twitter sign-in
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 Twitter 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 withFirebase Hosting:
Follow steps 1 through 3 inSet up your domain forHosting. When you verify
your domain ownership,Hostingprovisions an SSL certificate for your custom domain.
Add your custom domain to the list of authorized domains in theFirebaseconsole:auth.custom.domain.com.
In the Twitter 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 theauthDomainfield:
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 theAuthobject. You can then get the user's
basic profile information from theUserobject. SeeManage Users.
In yourFirebase Realtime DatabaseandCloud StorageSecurity Rules, you can
get the signed-in user's unique user ID from theauthvariable,
and use it to control what data a user can access.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,[]]
