I'm looking at ways to incorporate social logins to log in with accounts like Google/Facebook/Twitter, etc. into an authentication system that integrates web applications created on several different platforms. I'd like to hear your constructive feedback on whether the plan I'm currently considering is reasonable.
I am responsible for the program maintenance and ongoing refurbishment of the authentication system for a website system with one million members.
This website consists of more than 10 different applications with several different developping platforms. The core of the authentication system that integrates these applications was created in ASP.NET 4.0, and the basic part of the authentication is done using form authentication, not ASP.NET Identity.
Ninety percent of the members of this site are created based on the membership information provided by the companies that use the site's services, and 10 percent of the members are created by registering themselves as members.
As I mentioned first, I'm planning to incorporate social login into the website's authentication system, which allows users to log in with their Google/Facebook/Twitter accounts. For existing members, after entering the website after authentication, they will be able to set up social login from a dedicated page.
I would like to ask you all if I have the right idea for building this system. My plan is as follows.
advantage
Drawbacks.
I'm sure there are many examples of medium and larger web systems that embed social login functionality into existing authentication. I would be very happy to receive better methods and advice from those who have experienced this kind of development.
I have changed the place for this argument to the following thread inf ASP.NET Forum.
Please check above for the following arguments.
Thank you.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.