Autenticação anônima com o Firebase usando JavaScript
Mantenha tudo organizado com as coleções Salve e categorize o conteúdo com base nas suas preferências.
Você pode usar Firebase Authentication para criar e usar contas anônimas temporárias e fazer a autenticação no Firebase. Com essas contas, os usuários que ainda não se registraram no seu app podem trabalhar com os dados protegidos pelas regras de segurança. Se um usuário anônimo se registrar no seu app, vincule as credenciais de login à conta anônima para que ele continue trabalhando com os dados protegidos nas sessões futuras.
Na página Métodos de login, ative o método de login Anônimo.
Opcional: se o projeto teve upgrade para o Firebase Authentication with Identity Platform, você pode ativar a limpeza automática. Quando você faz isso, contas anônimas com mais de 30 dias são automaticamente excluídas. Em projetos com a limpeza automática ativada, a autenticação anônima não é mais contabilizada nos limites de uso ou nas cotas de faturamento. Consulte Limpeza automática.
Fazer a autenticação anônima no Firebase
Quando um usuário não conectado acessar um recurso do app que exige autenticação no Firebase, faça login dele anonimamente executando as etapas a seguir:
Chame o método signInAnonymously:
Web
import{getAuth,signInAnonymously}from"firebase/auth";constauth=getAuth();signInAnonymously(auth).then(()=>{// Signed in..}).catch((error)=>{consterrorCode=error.code;consterrorMessage=error.message;// ...});
Se o método signInAnonymously for concluído sem erros, o observador registrado em onAuthStateChanged será acionado. Em seguida, será possível acessar os dados da conta do usuário anônimo com o objeto User:
Web
import{getAuth,onAuthStateChanged}from"firebase/auth";constauth=getAuth();onAuthStateChanged(auth,(user)=>{if(user){// User is signed in, see docs for a list of available properties// https://firebase.google.com/docs/reference/js/auth.userconstuid=user.uid;// ...}else{// User is signed out// ...}});
firebase.auth().onAuthStateChanged((user)=>{if(user){// User is signed in, see docs for a list of available properties// https://firebase.google.com/docs/reference/js/v8/firebase.Uservaruid=user.uid;// ...}else{// User is signed out// ...}});
Quando um usuário anônimo se inscreve no seu app, ele pode continuar trabalhando com a nova conta. Por exemplo, você pode deixar no carrinho de compras dessa conta os itens adicionados antes do registro. Para isso, execute as seguintes etapas:
Quando o usuário se inscrever, conclua o fluxo de login do provedor de autenticação do usuário até a chamada de um dos métodos Auth.signInWith, mas sem incluir essa etapa. Por exemplo, use o token de ID do Google, o token de acesso do Facebook ou o e-mail e a senha.
Consiga um AuthCredential para o novo provedor de autenticação:
Se a chamada a link for realizada corretamente, a nova conta do usuário vai ter acesso aos dados do Firebase da conta anônima.
Limpeza automática
Se você fez upgrade do seu projeto para o Firebase Authentication with Identity Platform, será possível ativar a limpeza automática no console do Firebase. Quando esse recurso é ativado, você permite que o Firebase exclua automaticamente contas anônimas com mais de 30 dias. Em projetos com a limpeza automática ativada, a autenticação anônima não é contabilizada nos limites de uso ou nas cotas de faturamento.
Todas as contas anônimas criadas após a ativação da limpeza automática podem ser excluídas automaticamente a qualquer momento 30 dias após a criação.
As contas anônimas estarão qualificadas para exclusão automática 30 dias depois da ativação da limpeza automática.
Se você desativar a limpeza automática, todas as contas anônimas programadas para exclusão vão continuar dessa forma.
Se você fizer "upgrade" de uma conta anônima com vinculação a qualquer método de login, ela não vai ser excluída automaticamente.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Não contém as informações de que eu preciso","missingTheInformationINeed","thumb-down"],["Muito complicado / etapas demais","tooComplicatedTooManySteps","thumb-down"],["Desatualizado","outOfDate","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Problema com as amostras / o código","samplesCodeIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-08 UTC."],[],[],null,["You can use Firebase Authentication to create and use temporary anonymous accounts\nto authenticate with Firebase. These temporary anonymous accounts can be used to\nallow users who haven't yet signed up to your app to work with data protected\nby security rules. If an anonymous user decides to sign up to your app, you can\n[link their sign-in credentials to the anonymous\naccount](/docs/auth/web/account-linking) so that they can continue to work with their protected data in\nfuture sessions.\n\nBefore you begin\n\n1. [Add Firebase to your JavaScript project](/docs/web/setup).\n2. If you haven't yet connected your app to your Firebase project, do so from the [Firebase console](//console.firebase.google.com/).\n3. Enable anonymous auth:\n 1. In the [Firebase console](//console.firebase.google.com/), open the **Auth** section.\n 2. On the **Sign-in Methods** page, enable the **Anonymous** sign-in method.\n 3. **Optional** : If you've upgraded your project to [Firebase Authentication with Identity Platform](/auth#identity-platform), you can enable automatic clean-up. When you enable this setting, anonymous accounts older than 30 days will be automatically deleted. In projects with automatic clean-up enabled, anonymous authentication will no longer count toward usage limits or billing quotas. See [Automatic clean-up](#auto-cleanup).\n\nAuthenticate with Firebase anonymously\n\nWhen a signed-out user uses an app feature that requires authentication with\nFirebase, sign in the user anonymously by completing the following steps:\n\n1. Call the `signInAnonymously` method: \n\n Web \n\n ```javascript\n import { getAuth, signInAnonymously } from \"firebase/auth\";\n\n const auth = getAuth();\n signInAnonymously(auth)\n .then(() =\u003e {\n // Signed in..\n })\n .catch((error) =\u003e {\n const errorCode = error.code;\n const errorMessage = error.message;\n // ...\n });https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/snippets/auth-next/anonymous/auth_anon_sign_in.js#L8-L19\n ```\n\n Web \n\n ```javascript\n firebase.auth().signInAnonymously()\n .then(() =\u003e {\n // Signed in..\n })\n .catch((error) =\u003e {\n var errorCode = error.code;\n var errorMessage = error.message;\n // ...\n });https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/auth/anonymous.js#L9-L17\n ```\n This is also where you can catch and handle errors. For a list of error codes have a look at the [Auth Reference Docs](/docs/reference/js/firebase.auth.Auth#signInAnonymously).\n2. If the `signInAnonymously` method completes without error, the observer registered in the `onAuthStateChanged` will trigger and you can get the anonymous user's account data from the `User` object: \n\n Web \n\n ```javascript\n import { getAuth, onAuthStateChanged } from \"firebase/auth\";\n\n const auth = getAuth();\n onAuthStateChanged(auth, (user) =\u003e {\n if (user) {\n // User is signed in, see docs for a list of available properties\n // https://firebase.google.com/docs/reference/js/auth.user\n const uid = user.uid;\n // ...\n } else {\n // User is signed out\n // ...\n }\n });https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/snippets/auth-next/index/auth_state_listener.js#L8-L21\n ```\n\n Web \n\n ```javascript\n firebase.auth().onAuthStateChanged((user) =\u003e {\n if (user) {\n // User is signed in, see docs for a list of available properties\n // https://firebase.google.com/docs/reference/js/v8/firebase.User\n var uid = user.uid;\n // ...\n } else {\n // User is signed out\n // ...\n }\n });https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/auth/index.js#L43-L53\n ```\n\n| To protect your project from abuse, Firebase limits the number of new email/password and anonymous sign-ups that your application can have from the same IP address in a short period of time. You can request and schedule temporary changes to this quota from the [Firebase console](//console.firebase.google.com/project/_/authentication/providers).\n\nConvert an anonymous account to a permanent account\n\nWhen an anonymous user signs up to your app, you might want to allow them to\ncontinue their work with their new account---for example, you might want to\nmake the items the user added to their shopping cart before they signed up\navailable in their new account's shopping cart. To do so, complete the following\nsteps:\n\n1. When the user signs up, complete the sign-in flow for the user's authentication provider up to, but not including, calling one of the `Auth.signInWith` methods. For example, get the user's Google ID token, Facebook access token, or email address and password.\n2. Get an `AuthCredential` for the new authentication provider:\n\n Google Sign-In \n\n Web \n\n ```javascript\n import { GoogleAuthProvider } from \"firebase/auth\";\n\n const credential = GoogleAuthProvider.credential(\n googleUser.getAuthResponse().id_token);https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/snippets/auth-next/index/auth_make_google_credential.js#L8-L11\n ```\n\n Web \n\n ```javascript\n var credential = firebase.auth.GoogleAuthProvider.credential(\n googleUser.getAuthResponse().id_token);https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/auth/index.js#L13-L14\n ```\n\n Facebook Login \n\n Web \n\n ```javascript\n import { FacebookAuthProvider } from \"firebase/auth\";\n\n const credential = FacebookAuthProvider.credential(\n response.authResponse.accessToken);https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/snippets/auth-next/index/auth_make_facebook_credential.js#L8-L11\n ```\n\n Web \n\n ```javascript\n var credential = firebase.auth.FacebookAuthProvider.credential(\n response.authResponse.accessToken);https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/auth/index.js#L20-L21\n ```\n\n Email-password sign-in \n\n Web \n\n ```javascript\n import { EmailAuthProvider } from \"firebase/auth\";\n\n const credential = EmailAuthProvider.credential(email, password);https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/snippets/auth-next/index/auth_make_email_credential.js#L8-L10\n ```\n\n Web \n\n ```javascript\n var credential = firebase.auth.EmailAuthProvider.credential(email, password);https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/auth/link-multiple-accounts.js#L152-L152\n ```\n3. Pass the `AuthCredential` object to the sign-in user's\n `link` method:\n\n Web \n\n ```javascript\n import { getAuth, linkWithCredential } from \"firebase/auth\";\n\n const auth = getAuth();\n linkWithCredential(auth.currentUser, credential)\n .then((usercred) =\u003e {\n const user = usercred.user;\n console.log(\"Anonymous account successfully upgraded\", user);\n }).catch((error) =\u003e {\n console.log(\"Error upgrading anonymous account\", error);\n });https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/snippets/auth-next/link-multiple-accounts/auth_anonymous_link.js#L8-L17\n ```\n\n Web \n\n ```javascript\n auth.currentUser.linkWithCredential(credential)\n .then((usercred) =\u003e {\n var user = usercred.user;\n console.log(\"Anonymous account successfully upgraded\", user);\n }).catch((error) =\u003e {\n console.log(\"Error upgrading anonymous account\", error);\n });https://github.com/firebase/snippets-web/blob/467eaa165dcbd9b3ab15711e76fa52237ba37f8b/auth/link-multiple-accounts.js#L55-L61\n ```\n\nIf the call to `link` succeeds, the user's new account can\naccess the anonymous account's Firebase data.\n| This technique can also be used to [link any two accounts](/docs/auth/web/account-linking).\n\nAutomatic clean-up\n\nIf you've upgraded your project to [Firebase Authentication with Identity Platform](/docs/auth#identity-platform), you can\nenable automatic clean-up in the Firebase console. When you enable this feature you allow\nFirebase to automatically delete anonymous accounts older than 30 days. In projects with automatic\nclean-up enabled, anonymous authentication will not count toward usage limits or billing quotas.\n\n- Any anonymous accounts created after enabling automatic clean-up might be automatically deleted any time after 30 days post-creation.\n- Existing anonymous accounts will be eligible for automatic deletion 30 days after enabling automatic clean-up.\n- If you turn automatic clean-up off, any anonymous accounts scheduled to be deleted will remain scheduled to be deleted.\n- If you \"upgrade\" an anonymous account by linking it to any sign-in method, the account will not get automatically deleted.\n\nIf you want to see how many users will be affected before you enable this feature, and you've\nupgraded your project to [Firebase Authentication with Identity Platform](/docs/auth#identity-platform), you can filter by\n`is_anon` in [Cloud\nLogging](https://cloud.google.com/logging/docs).\n\nNext steps\n\nNow that users can authenticate with Firebase, you can control their access to\ndata in your Firebase database using\n[Firebase rules](/docs/database/security#section-authorization)."]]