▲ 4 points
Embedding browsers for 3rd party login – a security issue?
Many android apps (including Uber) allow facebook/google authentication. To do that, they open an embedded browser, with no address bar, where they show the facebook/google login page. You type your facebook/google credentials and they get the token.
While I understand what happens - an OAuth flow - embedding a browser without any address bar screams "phishing" to me. How do I know this is indeed google's login screen, and not Uber's exact copy, which collects my password?
Are there alternative, equally user-friendly ways to achieve the same? Maybe just showing the address bar?