Authenticate with Firebase using Password-Based Accounts on Android
Stay organized with collectionsSave and categorize content based on your preferences.
You can useFirebase Authenticationto let your users authenticate with
Firebase using their email addresses and passwords, and to manage your app's
password-based accounts.
On theSign in methodtab, enable theEmail/passwordsign-in
method and clickSave.
In yourmodule (app-level) Gradle file(usually<project>/<app-module>/build.gradle.ktsor<project>/<app-module>/build.gradle),
add the dependency for theFirebase Authenticationlibrary for Android. We recommend using theFirebase Android BoMto control library versioning.
dependencies{// Import theBoMfor the Firebase platformimplementation(platform("com.google.firebase:firebase-bom:34.2.0"))// Add the dependency for theFirebase Authenticationlibrary// When using theBoM, you don't specify versions in Firebase library dependenciesimplementation("com.google.firebase:firebase-auth")}
By using theFirebase Android BoM,
your app will always use compatible versions of Firebase Android libraries.
(Alternative)
Add Firebase library dependencies without using theBoM
If you choose not to use theFirebase BoM, you must specify each Firebase library version
in its dependency line.
Note that if you usemultipleFirebase libraries in your app, we strongly
recommend using theBoMto manage library versions, which ensures that all versions are
compatible.
dependencies{// Add the dependency for theFirebase Authenticationlibrary// When NOT using theBoM, you must specify versions in Firebase library dependenciesimplementation("com.google.firebase:firebase-auth:24.0.1")}
Create a password-based account
To create a new user account with a password, complete the following steps in
your app's sign-in activity:
In your sign-up activity'sonCreatemethod, get the shared
instance of theFirebaseAuthobject:
When initializing your Activity, check to see if the user is currently signed in:
Kotlin
publicoverridefunonStart(){super.onStart()// Check if user is signed in (non-null) and update UI accordingly.valcurrentUser=auth.currentUserif(currentUser!=null){reload()}}
@OverridepublicvoidonStart(){super.onStart();// Check if user is signed in (non-null) and update UI accordingly.FirebaseUsercurrentUser=mAuth.getCurrentUser();if(currentUser!=null){reload();}}
When a new user signs up using your app's sign-up form, complete any new
account validation steps that your app requires, such as verifying that the
new account's password was correctly typed and meets your complexity
requirements.
Create a new account by passing the new user's email address and password
tocreateUserWithEmailAndPassword:
Kotlin
auth.createUserWithEmailAndPassword(email,password).addOnCompleteListener(this){task->if(task.isSuccessful){// Sign in success, update UI with the signed-in user's informationLog.d(TAG,"createUserWithEmail:success")valuser=auth.currentUserupdateUI(user)}else{// If sign in fails, display a message to the user.Log.w(TAG,"createUserWithEmail:failure",task.exception)Toast.makeText(baseContext,"Authentication failed.",Toast.LENGTH_SHORT,).show()updateUI(null)}}
mAuth.createUserWithEmailAndPassword(email,password).addOnCompleteListener(this,newOnCompleteListener<AuthResult>(){@OverridepublicvoidonComplete(@NonNullTask<AuthResult>task){if(task.isSuccessful()){// Sign in success, update UI with the signed-in user's informationLog.d(TAG,"createUserWithEmail:success");FirebaseUseruser=mAuth.getCurrentUser();updateUI(user);}else{// If sign in fails, display a message to the user.Log.w(TAG,"createUserWithEmail:failure",task.getException());Toast.makeText(EmailPasswordActivity.this,"Authentication failed.",Toast.LENGTH_SHORT).show();updateUI(null);}}});
When initializing your Activity, check to see if the user is currently signed in:
Kotlin
publicoverridefunonStart(){super.onStart()// Check if user is signed in (non-null) and update UI accordingly.valcurrentUser=auth.currentUserif(currentUser!=null){reload()}}
@OverridepublicvoidonStart(){super.onStart();// Check if user is signed in (non-null) and update UI accordingly.FirebaseUsercurrentUser=mAuth.getCurrentUser();if(currentUser!=null){reload();}}
When a user signs in to your app, pass the user's email address and
password tosignInWithEmailAndPassword:
Kotlin
auth.signInWithEmailAndPassword(email,password).addOnCompleteListener(this){task->if(task.isSuccessful){// Sign in success, update UI with the signed-in user's informationLog.d(TAG,"signInWithEmail:success")valuser=auth.currentUserupdateUI(user)}else{// If sign in fails, display a message to the user.Log.w(TAG,"signInWithEmail:failure",task.exception)Toast.makeText(baseContext,"Authentication failed.",Toast.LENGTH_SHORT,).show()updateUI(null)}}
mAuth.signInWithEmailAndPassword(email,password).addOnCompleteListener(this,newOnCompleteListener<AuthResult>(){@OverridepublicvoidonComplete(@NonNullTask<AuthResult>task){if(task.isSuccessful()){// Sign in success, update UI with the signed-in user's informationLog.d(TAG,"signInWithEmail:success");FirebaseUseruser=mAuth.getCurrentUser();updateUI(user);}else{// If sign in fails, display a message to the user.Log.w(TAG,"signInWithEmail:failure",task.getException());Toast.makeText(EmailPasswordActivity.this,"Authentication failed.",Toast.LENGTH_SHORT).show();updateUI(null);}}});
Firebase Authenticationpassword policies support the following password requirements:
Lowercase character required
Uppercase character required
Numeric character required
Non-alphanumeric character required
The following characters satisfy the non-alphanumeric character requirement:^ $ * . [ ] { } ( ) ? " ! @ # % & / \ , > < ' : ; | _ ~
Minimum password length (ranges from 6 to 30 characters; defaults to 6)
Maximum password length (maximum length of 4096 characters)
You can enable password policy enforcement in two modes:
Require: Attempts to sign up fail until the user updates to a password
that complies with your policy.
Notify: Users are allowed to sign up with a non-compliant password. When
using this mode, you should check if the user's password complies with the
policy on the client side and prompt the user in some way to update their
password if it does not comply.
New users are always required to choose a password that complies with your
policy.
If you have active users, we recommend not enabling force upgrade on sign in
unless you intend to block access to users whose passwords don't comply with
your policy. Instead, use notify mode, which allows users to sign in with their
current passwords, and inform them of the requirements their password lacks.
Recommended: Enable email enumeration protection
SomeFirebase Authenticationmethods that take email addresses as parameters throw
specific errors if the email address is unregistered when it must be registered
(for example, when signing in with an email address and password), or registered
when it must be unused (for example, when changing a user's email address).
While this can be helpful for suggesting specific remedies to users, it can also
be abused by malicious actors to discover the email addresses registered by your
users.
To mitigate this risk, we recommend youenable email enumeration protectionfor your project using the Google Cloudgcloudtool. Note that enabling this
feature changesFirebase Authentication's error reporting behavior: be sure your app
doesn't rely on the more specific errors.
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, you can get the user's basic profile information from theFirebaseUserobject. 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,[]]