Esegui l'autenticazione con Firebase in modo anonimo utilizzando JavaScript
Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
Puoi utilizzare Firebase Authentication per creare e utilizzare account temporanei anonimi per autenticarti con Firebase. Questi account anonimi temporanei possono essere utilizzati per consentire agli utenti che non hanno ancora eseguito la registrazione alla tua app di lavorare con i dati protetti dalle regole di sicurezza. Se un utente anonimo decide di registrarsi alla tua app, puoi
collegare le sue credenziali di accesso all'account anonimo in modo che possa continuare a lavorare con i suoi dati protetti nelle
sessioni future.
Nella pagina Metodi di accesso, attiva il metodo di accesso Anonimo.
Facoltativo: se hai eseguito l'upgrade del progetto a Firebase Authentication with Identity Platform, puoi attivare la pulizia automatica. Se attivo questa impostazione, gli account anonimi che risalgono a oltre 30 giorni fa verranno eliminati automaticamente. Nei progetti in cui è attiva la pulizia automatica, l'autenticazione anonima non verrà più conteggiata ai fini dei limiti di utilizzo o delle quote di fatturazione. Vedi
Pulizia automatica.
Eseguire l'autenticazione con Firebase in forma anonima
Quando un utente che non ha eseguito l'accesso utilizza una funzionalità dell'app che richiede l'autenticazione con Firebase, fai in modo che acceda in modo anonimo completando i seguenti passaggi:
Chiama il metodo signInAnonymously:
Web
import{getAuth,signInAnonymously}from"firebase/auth";constauth=getAuth();signInAnonymously(auth).then(()=>{// Signed in..}).catch((error)=>{consterrorCode=error.code;consterrorMessage=error.message;// ...});
Se il metodo signInAnonymously viene completato senza errori, l'osservatore registrato in onAuthStateChanged
verrà attivato e potrai recuperare i dati dell'account dell'utente anonimo dall'oggetto 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// ...}});
Convertire un account anonimo in un account permanente
Quando un utente anonimo si registra alla tua app, potresti volergli consentire di continuare a lavorare con il suo nuovo account. Ad esempio, potresti rendere disponibili nel carrello del nuovo account gli articoli che l'utente ha aggiunto al carrello prima di registrarsi. Per farlo, segui questa procedura.
Quando l'utente si registra, completa la procedura di accesso per il fornitore di servizi di autenticazione dell'utente fino alla chiamata di uno dei metodi Auth.signInWith, esclusa questa operazione. Ad esempio, recupera il token ID Google,
il token di accesso di Facebook o l'indirizzo email e la password dell'utente.
Ricevi un AuthCredential per il nuovo provider di autenticazione:
Se la chiamata a link va a buon fine, il nuovo account dell'utente può accedere ai dati di Firebase dell'account anonimo.
Pulizia automatica
Se hai eseguito l'upgrade del progetto a Firebase Authentication with Identity Platform, puoi attivare il ripristino automatico nella console Firebase. Se attivi questa funzionalità, consenti a Firebase di eliminare automaticamente gli account anonimi che risalgono a oltre 30 giorni fa. Nei progetti in cui è attivata la pulizia automatica, l'autenticazione anonima non viene conteggiata ai fini dei limiti di utilizzo o delle quote di fatturazione.
Tutti gli account anonimi creati dopo l'attivazione della pulizia automatica potrebbero essere eliminati automaticamente
in qualsiasi momento dopo 30 giorni dalla creazione.
Gli account anonimi esistenti saranno idonei per l'eliminazione automatica 30 giorni dopo l'attivazione della pulizia automatica.
Se disattivi la pulizia automatica, gli account anonimi pianificati per l'eliminazione rimarranno pianificati per l'eliminazione.
Se esegui l'upgrade di un account anonimo collegandolo a qualsiasi metodo di accesso, l'account
non verrà eliminato automaticamente.
Ora che gli utenti possono autenticarsi con Firebase, puoi controllare il loro accesso ai dati nel tuo database Firebase utilizzando le
Regole Firebase.
[null,null,["Ultimo aggiornamento 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)."]]