How does general untying work after entering a system using Social Networks?

Asked

Viewed 65 times

-2

It is common for a user to "enter" into current systems using an account already registered on another network. The most common ones I see are facebook, google and etc..

The processo is simple and can be demonstrated as follows: inserir a descrição da imagem aqui

In that momento we may take some information from this user, such as login, email, tokens, id and other information provided in this integration. From there we can persist the data in our database, but even so we would be dependent on a password registration for the user to access the system without the integration of social networks.

When we solve the password problem in any way whatsoever, we can give rise to another problem because the user will have an access, but with information that can be removed from the system by the user. For let us suppose that: inserir a descrição da imagem aqui

When the user wants desvincular your network information used to log into the system. What would be the best approach to doing this? What care we should take, and what peculiarities to take care of when doing this?

Briefly my question would be: Given the many needs in integrating the access of users using social networks, which care should be taken when the user wants to unlink their information obtained on social networks of the system that deployed them.

  • 1

    Usually you retain the email, so the most likely approach is to keep everything, but only turn off the social network part by the token, the password keeps working, the email also and the username too, only you can no longer log in via social network. I did not deny, just to warn, but the question seems to me off-topic, a good place to ask would be the chat https://chatstack.exchange.com/rooms/11910/stackoverflow, but anyway I advanced what I understood and what seems reasonable, remembering if you choose only the token (no password) the person could return the link.

1 answer

1

As you have already said, usually the information that causes break in this situation is the Password, because the others theoretically are saved in the BD of your system. Most systems do not offer any information to the user after the unlinking, causing the user to deduct the process to "regularize" their account, which is usually:

Logout > I forgot my password > Login

This is a usability error that can be easily fixed by requiring the user to enter a new password to complete the unlinking.

Regarding the data collected, I believe it can be easily solved by allowing changes to the "profile page" according to your business rules. Normally this information can be changed even with a linked account, because the purpose is to speed up the user registration process, and not use them as "source of truth".

Browser other questions tagged

You are not signed in. Login or sign up in order to post.