Firebase does not Remember Auth on iOS added to HomeScreen - firebase

Firebase does remember and auto-login when I visit the site on mobile safari. However, when I add the app to iOS home screen, it does not seem to auto login anymore.
Home screen apps may clear cookies each time on load.
Is there anyway to get it to auto login as a homescreen app?
Thanks!!

[Engineer at Firebase] Note that Firebase Simple Login is a separate service built on top of Firebase Authentication, intended to simplify authenticating users and generating Firebase Auth. Tokens for use in Security Rules.
Update 2014/03/07: Support for redirect-based OAuth has been added to the Firebase Simple Login Web Client as of v1.3.0, available from the Firebase CDN or via Bower using bower install firebase-simple-login. This update enables the Simple Login client to automatically detect iOS "standalone" applications and handle the redirect-based OAuth automatically.
There is an existing bug at https://github.com/firebase/firebase-simple-login/issues/7 to add support for a redirect-based authentication flow, which is required to support iOS standalone-webview apps.

Related

PWA with Windows Authentication

On the high level, I have a PWA with React frontend and .netcore backend. I use service worker for caching and offline ability, in conjunction with workbox plugins for some precaching feature.
The app uses Windows Authentication. Which works fine if it wasn't a PWA app. It also works fine the first time the PWA app launches, I get the username, password login popup.
However from the second time visiting the app, it wouldn't show the login popup, the app fails at pulling data from the backend because it is unauthenticated. One weird behavior is that, if I open Chrome Dev Tools(by F12), then the login popup immediately shows up.
I thought it's caching related and somehow the service worker interfered with the server side authentication workflow. Maybe because the index page is cached by the workbox precache plugins, and it did not cache with the fetch header of 'credentials': 'include'? I tried adding the fetch option to other api routes, which are cached by workbox plugin RegisterRoute. However I didn't find a way to add it to the precacheAndRoute(self.__WB__MANIFEST). Wondering if that's the problem. But I'm also not sure why having Dev Tools open would trigger the popup to display.
Any input is appreciated.

Facebook login with firebase in react native app

I want to add Facebook login in the react native app(Android/IOS). I have created IOS and Android apps on Facebook developer account both apps have different App ID and different App secret. And on Firebase console I have enabled 'Facebook sign-in method' which takes only one App ID and one App secret. So which App ID and App secret should I put in the firebase console. Thanks in advance!!
I Found out the answer. Instead of creating 2 different apps i.e IOS and Android version on the Facebook developer account create one app and then click 'add platform' option on Facebook developer account.

Facebook Logon not working properly with Azure Mobile Client in Xamarin.Forms

I'm implementing Facebook Logon with Azure Mobile Client in Xamarin.Forms. In iOS, after entering login name and password, it directed to the confirmation page but I couldn't click anything on the screen. The loading icon kept running and should represent that the loading hadn't completed yet. Anyone encountered similar situation and anything I could do to fix it?
There are/were issues with Facebook auth on Azure App Service due to a deprecation in the Facebook side of the OAuth dance. See https://social.msdn.microsoft.com/Forums/en-US/397f6952-57bf-4c28-b383-6bba08d28f9a/facebook-login-failures-with-app-service-authentication-authorization?forum=windowsazurewebsitespreview for more details.

ASP.NET Web-API Facebook login

I'm developing an Android App with an ASP.NET Wep-API Backend. Currently i have problems with the Facebook login. I want to login the users with the FB Access Token i get by the Facebook Android SDK. Is this possible? I thought i read something about that this is possible without a workarround by directly post the token to the /signin-facebook endpoint, but i can't find that solution anymore. So here is my question:
Is it possible to login/register to an ASP.NET Web-API directly with the facebook token? Or do i have to implement a workaround?
Best regards
The Web API comes with OWIN which then allowing you to implement (or activate) Access token login. You need to register to Facebook developer in order to get the app Id and secret key.
You can install in your web api project using nuget:
Install-Package Microsoft.Owin.Security.Facebook -Version 2.1.0
More detail.. you can try follow the link here

What will be the Firebase Authorized Domain for Firefox Packaged App?

My packaged app for Firefox OS uses Firebase and Firebase Facebook Login for user authentication. However, in Firebase I need to provide a Authorized domain for oauth redirect. What will be my Authorized domain for a Firefox OS packaged app?
I ran this app in the FF OS simulator through FF WebIDE and from there I got an app id which I used as a Aauthorized domain in Firebase and it (fb login) worked. But then I submitted my packaged app in the Firefox marketplace and got rejected as Facebook Login is not working.
What am I missing here?
I would guess it works via the simulator because you are on localhost, which is whitelisted in your account dashboard. Naturally, you aren't going to be able to create a whitelisted domain that works within the packaged app.
Instead, to make integrated auth work, you'd need to set up a hosted login page and feature that in your app, then you can whitelist the hosted page instead. For example, if you hosted your login form at yourinstance.firebaseapp.com:
Whitelist yourinstance.firebaseapp.com
App redirects to or "iframes" https://yourinstance.firebaseapp.com/login.html
When login is completed, login.html returns the userData.token to packaged app
Packaged app calls authWithCustomToken(token)
Alternately, and possibly a much simpler and more elegant solution, you could sign your own tokens and utilize those in the packaged app.

Resources