3 ms·
> It's a massive waste of time and developer energy considering these forms almost universally require the same input: name, profile icon, email, password. The
by mschuster91 7y ago
> It's a massive waste of time and developer energy considering these forms almost universally require the same input: name, profile icon, email, password.
There's more to a user login/registration flow, way more, and that list is only what I could manage to write down in 5 minutes:
1. Support for a variety of custom 2FA methods - SMS, Yubikey/other tokens, RSA dongles, chip-TAN (used by German Sparkasse credit unions, works with an external chip reader), phone calls, the list is endless
2. Support for GDPR compliance (i.e. double opt in confirmation of email addresses)
3. Support for SSO solutions, with the added complexity that each app needs their own set of tokens for each social network
4. Support for password recovery in all the loads of combinations
5. Support for enterprise authentication (SAML / shibboleth)
- nexuist 7y agoSure! I agree. There are plenty of different authentication standards. But if these are all highly ubiquitous standards implemented by a myriad of apps, why is this work passed on to the developer, and not handled by the operating system? Why can't I pass my OAuth tokens to this hypothetical login view (a la Firebase Auth), and let that handle signing my user in through X service? Why can't I just provide a shibboleth endpoint and let the native view handle exchanging tokens? I'm not asking Apple or Google to figure out my highly custom one-and-done authentication protocol that relies on smoke signals and written poems to let the user sign in. I'm asking them to give me the tools to support these decades-old standards, standards that basically every app has to support already. It makes sense especially in the context of GDPR to provide system-wide support to a legal problem, as opposed to each developer having to solve the same exact problem over and over again.