Melakukan Autentikasi dengan Firebase secara Anonim Menggunakan C++
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Anda dapat menggunakan Firebase Authentication untuk membuat dan menggunakan akun anonim sementara untuk melakukan autentikasi dengan Firebase. Dengan akun anonim sementara ini, pengguna yang belum mendaftar ke aplikasi Anda dapat menggunakan data yang dilindungi oleh aturan keamanan. Jika pengguna anonim memutuskan untuk mendaftar ke aplikasi Anda, tautkan kredensial login mereka ke akun anonim tersebut agar mereka dapat terus menggunakan data yang dilindungi tersebut pada sesi-sesi selanjutnya.
Di halaman Sign-in Methods, aktifkan metode login Anonymous.
Opsional: Jika Anda telah mengupgrade project ke
Firebase Authentication with Identity Platform, Anda dapat mengaktifkan pembersihan otomatis. Saat setelan ini diaktifkan, akun anonim yang berusia lebih dari 30 hari akan otomatis dihapus. Dalam project yang mengaktifkan pembersihan otomatis, autentikasi anonim tidak akan diperhitungkan lagi dalam batas penggunaan atau kuota penagihan. Lihat Pembersihan otomatis.
Melakukan autentikasi dengan Firebase secara anonim
Ketika pengguna yang tidak login menggunakan fitur aplikasi yang mengharuskan autentikasi menggunakan Firebase, buat agar pengguna tersebut login secara anonim dengan mengikuti langkah-langkah berikut:
Class Auth adalah gateway untuk semua panggilan API.
Tambahkan file header Auth dan App:
#include"firebase/app.h"#include"firebase/auth.h"
Pada kode inisialisasi Anda, buat class firebase::App.
Jika program Anda memiliki loop pembaruan yang berjalan secara teratur (misalnya 30 atau 60 kali per detik), Anda dapat memeriksa hasilnya satu kali per pembaruan dengan Auth::SignInAnonymouslyLastResult:
firebase::Future<firebase::auth::AuthResult>result=auth->SignInAnonymouslyLastResult();if(result.status()==firebase::kFutureStatusComplete){if(result.error()==firebase::auth::kAuthErrorNone){firebase::auth::AuthResultauth_result=*result.result();printf("Sign in succeeded for `%s`\n",auth_result.user.display_name().c_str());}else{printf("Sign in failed with error '%s'\n",result.error_message());}}
Ketika pengguna anonim mendaftar ke aplikasi, Anda dapat mengizinkannya melanjutkan aktivitas dengan akun yang baru dibuat. Misalnya, Anda mungkin menginginkan agar item yang ditambahkan pengguna ke keranjang belanja sebelum mendaftar tersedia di keranjang belanja pengguna pada akun yang baru. Caranya, ikuti langkah-langkah berikut:
Ketika pengguna mendaftar, selesaikan alur login untuk penyedia autentikasi pengguna tersebut hingga, tetapi sebelum, memanggil salah satu metode Auth::SignInWith. Misalnya, dapatkan token ID Google, token akses Facebook, atau alamat email dan sandi pengguna tersebut.
Dapatkan auth::Credential untuk penyedia autentikasi baru:
Teruskan objek auth::Credential ke metode LinkWithCredential pengguna yang login:
// Link the new credential to the currently active user.firebase::auth::Usercurrent_user=auth->current_user();firebase::Future<firebase::auth::AuthResult>result=current_user.LinkWithCredential(credential);
Jika panggilan ke LinkWithCredential berhasil, akun baru pengguna dapat mengakses data Firebase akun anonim.
Pembersihan otomatis
Jika Anda telah mengupgrade project ke Firebase Authentication with Identity Platform, Anda dapat mengaktifkan pembersihan otomatis di Firebase console. Jika fitur ini diaktifkan, Firebase akan otomatis menghapus akun anonim yang berusia lebih dari 30 hari. Dalam project yang mengaktifkan pembersihan otomatis, autentikasi anonim tidak akan diperhitungkan dalam batas penggunaan atau kuota penagihan.
Setiap akun anonim yang dibuat setelah pembersihan otomatis diaktifkan dapat otomatis dihapus dalam waktu 30 hari setelah dibuat.
Akun anonim yang ada akan memenuhi syarat untuk penghapusan otomatis 30 hari setelah pembersihan otomatis diaktifkan.
Jika Anda menonaktifkan pembersihan otomatis, akun anonim yang dijadwalkan untuk dihapus akan tetap dijadwalkan untuk dihapus.
Jika Anda "mengupgrade" akun anonim dengan menautkannya ke metode login apa pun, akun tersebut tidak akan otomatis dihapus.
Jika ingin melihat jumlah pengguna yang akan
terkena dampaknya jika Anda mengaktifkan fitur ini, dan Anda telah
mengupgrade project ke Firebase Authentication with Identity Platform, Anda dapat memfilter berdasarkan
is_anon di Cloud
Logging.
Langkah berikutnya
Setelah pengguna dapat melakukan autentikasi dengan Firebase, Anda dapat mengontrol akses mereka ke data di database Firebase Anda menggunakan aturan Firebase.
[null,null,["Terakhir diperbarui pada 2025-08-16 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/cpp/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 C++\n project](/docs/cpp/setup#note_select_platform).\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:\nThe `Auth` class is the gateway for all API calls.\n\n1. Add the Auth and App header files: \n\n ```c++\n #include \"firebase/app.h\"\n #include \"firebase/auth.h\"\n ```\n2. In your initialization code, create a [`firebase::App`](/docs/reference/cpp/class/firebase/app) class. \n\n ```c++\n #if defined(__ANDROID__)\n firebase::App* app =\n firebase::App::Create(firebase::AppOptions(), my_jni_env, my_activity);\n #else\n firebase::App* app = firebase::App::Create(firebase::AppOptions());\n #endif // defined(__ANDROID__)\n ```\n3. Acquire the `firebase::auth::Auth` class for your `firebase::App`. There is a one-to-one mapping between `App` and `Auth`. \n\n ```c++\n firebase::auth::Auth* auth = firebase::auth::Auth::GetAuth(app);\n ```\n\n- Call `Auth::SignInAnonymously`. \n\n ```c++\n firebase::Future\u003cfirebase::auth::AuthResult\u003e result =\n auth-\u003eSignInAnonymously();\n ```\n- If your program has an update loop that runs regularly (say at 30 or 60 times per second), you can check the results once per update with `Auth::SignInAnonymouslyLastResult`: \n\n ```c++\n firebase::Future\u003cfirebase::auth::AuthResult\u003e result =\n auth-\u003eSignInAnonymouslyLastResult();\n if (result.status() == firebase::kFutureStatusComplete) {\n if (result.error() == firebase::auth::kAuthErrorNone) {\n firebase::auth::AuthResult auth_result = *result.result();\n printf(\"Sign in succeeded for `%s`\\n\",\n auth_result.user.display_name().c_str());\n } else {\n printf(\"Sign in failed with error '%s'\\n\", result.error_message());\n }\n }\n ```\n Or, if your program is event driven, you may prefer to [register a callback on the\n Future](#register_callback_on_future).\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- When an anonymous user signs up to your app, you might want to allow them to continue their work with their new account---for example, you might want to make the items the user added to their shopping cart before they signed up available in their new account's shopping cart. To do so, complete the following steps:\n 1. 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.\n 2. Get an `auth::Credential` for the new authentication provider:\n\n **Google Sign-In** \n\n ```c++\n firebase::auth::Credential credential =\n firebase::auth::GoogleAuthProvider::GetCredential(google_id_token,\n nullptr);\n ```\n **Facebook Login** \n\n ```c++\n firebase::auth::Credential credential =\n firebase::auth::FacebookAuthProvider::GetCredential(access_token);\n ```\n **Email-password sign-in** \n\n ```c++\n firebase::auth::Credential credential =\n firebase::auth::EmailAuthProvider::GetCredential(email, password);\n ```\n 3. Pass the `auth::Credential` object to the sign-in user's\n `LinkWithCredential` method:\n\n ```c++\n // Link the new credential to the currently active user.\n firebase::auth::User current_user = auth-\u003ecurrent_user();\n firebase::Future\u003cfirebase::auth::AuthResult\u003e result =\n current_user.LinkWithCredential(credential);\n ```\n- If the call to `LinkWithCredential` succeeds, the user's new account can access the anonymous account's Firebase data.\n| This technique can also be used to [link any two accounts](/docs/auth/cpp/account-linking).\n\nAutomatic clean-up\n- If you've upgraded your project to [Firebase Authentication with Identity Platform](/docs/auth#identity-platform), you can enable automatic clean-up in the Firebase console. When you enable this feature you allow Firebase to automatically delete anonymous accounts older than 30 days. In projects with automatic clean-up enabled, anonymous authentication will not count toward usage limits or billing quotas.\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- If you want to see how many users will be affected before you enable this feature, and you've upgraded your project to [Firebase Authentication with Identity Platform](/docs/auth#identity-platform), you can filter by `is_anon` in [Cloud\n Logging](https://cloud.google.com/logging/docs).\n\nNext steps\n- Now that users can authenticate with Firebase, you can control their access to data in your Firebase database using [Firebase rules](/docs/database/security#section-authorization)."]]
