firebase / firebase/firebase-cpp-sdk
[Question] Disable auto-login in Firebase?
- Langage dominant
- C++
- Étoiles
- 326
- Forks
- 137
- Merge moyen
- 3 j 9 h
- PR mergées (30 j)
- 5
Description
### [READ] For Firebase Unity SDK question, please report to [Firebase Unity Sample](https://github.com/firebase/quickstart-unity/issues/new/choose)
Once you've read this section and determined that your issue is appropriate for this repository, please delete this section.
### [REQUIRED] Please fill in the following fields:
* Pre-built SDK from the [website](https://firebase.google.com/download/cpp) or open-source from this repo: **pre-built SDK**
* Firebase C++ SDK version: **12.7.0**
* Main Firebase Components in concern: **Auth** (Auth, Database, etc.)
* Other Firebase Components in use: _____ (Auth, Database, etc.)
* Platform you are using the C++ SDK on: **Ubuntu 24.04** (Mac, Windows, or Linux)
* Platform you are targeting: **Desktop** (iOS, Android, and/or desktop)
### [REQUIRED] Please describe the question here:
I want to disable auto-login, that is, I want to make that when the user opens my Desktop application `current_user()->is_valid()` evaluates to `false` (no currently active user).
At the moment the authentication state looks like to persist, I've tried avoiding this by signin-out as soon as I connect to the API:
```c++
m_firebase_app = firebase::App::Create(app_options);
m_firebase_auth = firebase::auth::Auth::GetAuth(m_firebase_app);
m_firebase_auth->SignOut();
m_firebase_auth->current_user().is_valid(); // Is still true with valid uid/email
```
But it does not work.
Another question: where is the authentication persisted on my local filesystem (which path)?
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par les appels à firebase::App::Create, firebase::auth::Auth::GetAuth, SignOut() et current_user() présentés dans le rapport. Examinez l’implémentation desktop de Auth et son comportement de persistance afin de déterminer si la connexion automatique peut être désactivée et où les identifiants sont stockés ; le travail est terminé lorsque des réponses confirmées aux deux questions sont fournies.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- cpp, firebase
- Domaine
- authentication, desktop
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 30/100