Auth0 login on android device without web browser

Hi!

I’m developping an native android app used by employees of a company only, the app is not public. And they are supposed to use their google work account to log in. The issue is that the app should run on a all-in-one bank terminal running on android, and for security concern, the device doesn’t have any web browser (and can’t be installed). Is it possible to run the universal login in a webview rather than an external browser? Should I use legacy embedded solutions like Lock.Android instead?

Thanks for the help!

Hi @jeantuffier

Welcome to the Auth0 Community!

You are asking whether Universal Login can run inside an embedded WebView on a bank terminal that has no web browser, so employees can sign in with their Google work accounts, and whether the legacy Lock.Android SDK is a better option.

Google Blocks OAuth Requests Made Via Embedded Browsers, including WebViews. Universal Login running in a WebView will fail when the user selects Google, and Lock.Android also fails in WebView mode for the same reason. Switching to Lock.Android does not solve the problem.

I hope that I understood your flow correctly and the above resources provide some information, albeit not the outcome that we hoped for. I would recommend that you submit a Feature Request on this matter, but since it appears to be inherently blocked by Google, any workaround would require the use of web browsers, which does not suit your use case.
Hope this provided some clarity!

Best regards,
Gerald

Hi @gerald.czifra !

I think I found a solution though with calling Auth0 APIs myself rather than using the Android SDK. I first call “https://{domain}/passwordless/start“ and then “https://{domain}/oauth/token“. With this, I successfully obtain a token. Don’t you think it would be enough? I followed the instructions here Using Passwordless APIs - Auth0 Docs.

Edit : I was probably not clear in my explanation. When I said “they are supposed to use their google work account”, I meant their work email, not neccessarly a SSO with their Google account, which would have been even nicer though.