I know that Google's Firebase/Firestore platform supports multiple authentication methods/backends, but I'm not currently seeing any option for Fido2 or WebAuthn for Firebase Authentication. Does anyone know if Google has a timeline to release support for Fido2 on their Firebase development platform? Or if it's already available, and I'm just missing something.
I am currently only on the Spark FREE plan, so I don't know if that is a problem.
Any insight or assistance would be much appreciated.
Cheers!
They currently do not support it, and as far as I can tell there's currently no timeline for support. source
Google has recently started using the WebAuthn API for authentication of security keys, but not yet for registration. I would guess that Firebase gets passwordless authentication support around the same time that Google accounts do, but I couldn't say if that's 3 months or 3 years away.
Related
I'm developing a flutter application which uses Firebase as its framework. One of Firebase's features that we use is App Check. I've been using SafetyNet for my Android App Check, but recently I've gotten an email from Google that states that SafetyNet will be discontinued and developers are recommended to migrate to Play Integrity. The problem is, I don't know how to do so, I've tried changing it directly from Firebase Console, and now both my Play Integrity and SafetyNet option is checked, last time it was only SafetyNet. Are there any steps that I might've missed? Any help would be greatly appreciated.
For the last couple of days, I have faced an issue with my Unity project regarding adding Google and Facebook authentication for my users, using Firebase. The thing is that there exist a couple of youtube tutorials for each of those two implementations but they are quite misleading and rushed.
Apart from that those tutorials refer to the creation of a new project which implies that the Firebase Auth package is not yet installed. And I mention this because I've seen plenty of people in the comments that are struggling with the Plugins and Parse folders that get overwritten whenever both Firebase Auth and Google or Facebook packages are installed. So there does not exist a rule of thumb on how to proceed in cases where projects already had other methods of authentication such as Email/Password.
Of course, the documentation for both Google and Facebook is unclear on how to get the access token.
Facebook SignIn doc: https://firebase.google.com/docs/auth/unity/facebook-login?hl=en&authuser=0
Google SignIn doc:
https://firebase.google.com/docs/auth/unity/google-signin?hl=en&authuser=0
I've made this post in order to find a step-by-step solution to my problem and hopefully help the community find a solution to a problem that concerns many developers.
[Edit]: My question is. How exactly do I implement the Google & Facebook Sign-In, based on the documentation, that is unclear, especially on the step
Follow instructions for Android and iOS+ to get an access token for the signed-in Facebook user.
And I am speaking for a project that already has imported Firebase.Authentication, which means that folders such as Plugins and Parse are already in the Assets and get overloaded from the packages requested by the 'tutorials' (Because the docs do not even mention what package to use and how).
[Edit]: As of right now I've managed to set up the code in a way that has no errors. When I run it though I get:
[Android]: Exception: Field currentActivity or type signature not found.
[iOS]: EntryPointNotFoundException: GoogleSignIn_Create
After some googling, they proposed testing it after I build it which I think is way too much time-consuming.
This is the answer I've got from Firebase support.
First of all, we need to note that Firebase only has three native authentication providers: email, phone, and anonymous authentication. For the other methods, Firebase needs to trust how their respective third-party providers handle their authentication flow. That's why Firebase can't offer a way to get the access token. This is not its responsibility.
So, to sign in with a Federated provider (FP) you must follow the following steps.
Think about which will be your target mobile platform. Not all the FP provide the same authentication flow on iOS or Android. For example Google offers a more handy way to authenticate Android devices by using Google Play Game Services
Authenticate in Unity Using Google Play Games Services | Firebase
Search on his FP's official GitHub repository for the official plugins to get access to the FP's SDK on Unity. For example, Google offer a useful plugin to authenticate user in both platforms
GitHub - googlesamples/google-signin-unity: Google Sign-In API plugin for Unity game engine. Works with Android and iOS.
Last plugin's release: https://github.com/googlesamples/google-signin-unity/releases/tag/v1.0.4
Examples - Unity SDK - Documentation - Meta for Developers
Create the FP credentials according to its own requirements. For example, Google login requires the use of web_client_id, which can be obtained from the google-services.json or GoogleService-Info.plist files needed to build the application on the target platform.
https://github.com/googlesamples/google-signin-unity#get-a-google-sign-in-configuration-file
https://github.com/googlesamples/google-signin-unity#using-this-plugin-with-firebase-auth
Once you've built the FP's credential into your project, it's time to check out our Firebase documentation for using the FP credential in our authentication flow. I recommend having the Firebase reference along with the documentation as it will help to know what arguments the required method needs.
The best way to test your new authentication provider is by implementing the Firebase Authentication Unity Quickstart. Please clone the Unity Quickstart repository here and deploy the Unity project found in the auth folder. Follow the steps mentioned in the README.md file and build the app on your target platform.
I recommend that you add the FP's SDK right in the same step as adding the Firebase SDK plugins to avoid some build issues. Since these errors are more related to Unity than Firebase, I recommend reaching out to our communities on StackOverflow, Google Groups, and Slack for help with these issues as they have more knowledge than I on those topics.
So, in conclusion, getting credentials from third-party providers is a task delegated to them and not to Firebase since this one is not responsible for any third-party authentication flow.
I'm trying to delete version from my crashlytics tab as they are not necessary.
I've already seen this post which exactly what I need but for Firebase, this new app isn't on Fabrics as they'll migrate to Firebase in a month or so.
I haven't been able to find the same functionality as in Fabrics. If anyone knows that would be really helpful.
As of today, after reaching to Firebase support, I got this answer:
We have received similar requests to add support for enabling and disabling the monitoring of a specific version of your app. I've raised your request to our engineering team, and this will be evaluated for consideration. However, I cannot guarantee when this feature will be officially rolled out.
For now, you may keep an eye out on our Firebase blog or release notes for any latest news or new features that we may have. We appreciate that you have expressed your feedback as this makes Firebase a better place for everyone.
I am currently working on the old project. I am having the whole working android project but I am not aware which firebase account is my android project linked with. Please help!!
I want to know where I can find the developer email address of the firebase account.
Information about the developer of the project is not exposed on the configuration data that is included in the app. If this was possible, it would actually be a security risk as any user of your app could then find that email address.
If you are the developer yourself, but forgot which email address you used to sign in to the Firebase console, reach out to Firebase support for personalized help in troubleshooting. If you're not the developer, I'm afraid there's not much they (or any of us) can do.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Here the "List" of firebase features
Analytics
Cloud Messaging
Remote Config
Dynamic Links
Notifications
Invites
Test Lab
Crash Reporting
AdMob
Storage
Realtime Database
Google AdWords
Authentication
App Indexing
However, at least, some of them don't work properly and some do not work at all with react-native.
Let's share here our experience dealing with all these services. I hope, that will clarify, what exactly FB is good for with react-native app.
I'll be storing summary here:
Analytics
Likely supported with third-party library
Cloud Messaging
Likely supported with third-party library
Remote Config
Not supported
Dynamic Links
Not supported
Notifications
Likely supported with third-party library
Invites
Not supported
Test Lab
Not supported
Crash Reporting
Likely supported with third-party library
AdMob
Likely supported with third-party library
Storage
I guess, now it's fully supported?
Realtime Database
Web (JS) SDK does not support: offline data persistence
Google AdWords
Authentication
Google, Facebook (etc.) auth is not supported at all. Possible solutions include third-party libraries, firebase-native-sdk bridges etc. There are not well documented solution atm.
App Indexing
Likely supported with third-party library
Check out react-native Firestack. Its currently being worked on but most features are supported for both Android and iOS. I recently used this react-native library for a production application for my company and supports many of the options you listed that you believed were not supported. According to the documentation Firestack provides
Complete FirebaseModule functionality
I have used Firebase authentication, Facebook authentication, Firebase storage, Firebase database, and Firebase notifications all with the Firestack framework.
Another reason I would use this library is it contains the individual modules you listed above but in a centralized repository so you do not have to import many different libraries and deal with their possible incompatibilities and differences in syntax.
https://github.com/davecoates/rn-firebase-bridge/
Here is another one. React Native Firebase Bridge which supports Persistent data. You guys wanna check it out.