firebase-authentication

问题 I have a Firebase database connected to my IOS app with the GoogleService-Info.plist. In AppDelegate I configured the App FIRApp.configure(). I could read/write data. Now, from within this IOS app, I would like to access another FireBase Database brevCustomer . For some reason let dbRef from viewDidLoad has a flag in Xcode saying this 'immutable value dbRef was never used' and the app crashes on the first line in fun startObserving() dbRef.observe(.value, with: { (snapshot: FIRDataSnapshot)

问题 This question already has answers here : Create group access to firebase storage without using custom authorization (3 answers) Closed 3 years ago . I am trying to restrict firebase storage based on user role. Database: users <uid> admin=false ... ... ... I am trying to use the following kind of rule in firebase storage: root.child('users').child(auth.uid).child('user').child('admin').val() == true I am getting access denied after adding this to the write rule. Thanks. 回答1: As Frank van

问题 When using Firebase's Email & Password setting it seems like there are no security constraints on the password. For example I could create the following user: firebaseRef.createUser( { email: "john.doe@example.org", password: "j" }); I'd like to at least set a minimum password length. Does firebase provide a way to do this? 回答1: There is currently no way to configure a minimum password length or strength for Firebase email+password Authentication. You could build such a restriction into your

问题 I knew that we can verify the users email with Firebase Auth 3.0. I'm not able to find any documentation regarding email verification on Android. I'm able to find the same for iOS as well as web but not for Android. Any link to the documentation would be helpful. From the image, it is clear that once the user signs in, he will be intimated regarding that on email to confirm his subscription. I've subscribed myself and also verified in the users section in Auth tab and I am able to see my mail

问题 Firebase auth was working fine, the debug build suddenly started failing without any change of code, logging the folloing message D/PhoneAuthActivity( 7392): signInWithCredential:failure:com.google.firebase.auth.FirebaseAuthException: This app is not authorized to use Firebase Authentication. Please verifythat the correct package name and SHA-1 are configured in the Firebase Console. [ App validation failed ]. The only notable action inbetween a successful login and failure is android studio

问题 So, there are a couple similar questions on here, but none of them have a working solution for me. I am using the Quickstart demo downloaded from Github. Downloaded today. I've changed nothing in the demo code. Some common mistakes (from what I've read) that I've addressed: I have the project created in the Firebase Console with the downloadable json file (created with package name). I have provided my SHA1 fingerprint. Email/Password sign-in method is checked. I have Google Play Services and

问题 I'm using the firebase node api in my javascript files for Google login. firebase.initializeApp(config); let provider = new firebase.auth.GoogleAuthProvider(); firebase.auth().signInWithPopup(provider); This works fine and the user is able to login with his Google credentials. When the user visits the page again, the popup opens again but since he has already logged in, the popup closes without requiring any interaction from the user. Is there any way to check if there is already a logged in

问题 After I manually deleted the account connected to the uid that my iphone simulator is on (from firebase dashboard), when I run the code below it's somehow still authenticating and retrieving a uid. How is this possible? let ref = Firebase(url: "https://moviebuffapp.firebaseio.com/") override func viewDidLoad() { super.viewDidLoad() if ref.authData != nil { let uid = ref.authData.uid print(uid) 回答1: Deleting an account does not automatically expire the current session(s) for that account.

问题 For my understanding, Google Identity toolkit provides a layer for login with different accounts, like Facebook, Yahooo etc. but how does that differ from then Google OAuth implementation? And regarding Google+ sign in, it is still using the OAuth, but only enable login for Google accounts? 回答1: Update as of December 28, 2018 : Google is pushing a new service called Cloud Identity Platform. Which is basically Firebase Authentication just for all GCP customers. This service offers, like

问题 There doesn't seem to be any mention of this in the documentation, and all I found was this and this, where I would like to confirm this: If there is an existing account with the same email address but created with other credentials (e.g. password or non-trusted provider), the previous credentials are removed for security reasons. If a user signs in through Facebook or email/password and later through Google, their account sign in method is converted to Google. It only happens with Google and