0
Imagine the following scenario:
You are setting up a project where anyone can register with basic data (name, photo, age) to use your product. And as it is on the internet there is no way to predict the number of potential users who can sprout overnight.
Well, thinking about this aspect, I would like to know if it is worth using the Apis provided by companies such as Facebook, Twitter and Google to access the data of these users (oAuth), or if yet it is worth keeping the traditional login style, providing a method of registering the user and storing their information on a server of their own.
In my opinion, apparently the strengths of using Uth would be:
- User registration facility;
- Speed in obtaining data;
- Resource savings (since data comes via external API);
- Data always up to date;
But since I never messed with this type of API I honestly don’t know if it’s worth it or not, so, mainly from a scalability point of view, it’s worth using oAuth Apis or conventional login (own bank)?
just a note, read this news, because it is likely that authentication via Oauth starts to be little used for some time, maybe users use less because of this failure that you will find better in the news. http://www.techtudo.com.br/noticias/noticia/2014/05/safetyfailure-affectingbook-google-e-microsoft.html
– Enzo Tiezzi
@Enzotiezzi believe that there are still more flaws that have not been discovered, however it is worth mentioning the ability that Facebook has to solve the problems and even so still has more credibility than a system of its own.
– Filipe Moraes
@Filipe Yes, it was just a touch to see if it would affect something in its development.
– Enzo Tiezzi