OAuth2.0 is the next version of the OAuth protocol, but it is not backward compatible with OAuth1.0 and completely abolishes OAuth1.0. OAuth2.0 focuses on simplicity for client developers. Either by structuring approved interactions between the resource owner and the HTTP provider on behalf of the user, or by allowing third-party applications to gain access on the user's behalf. It also provides dedicated certification processes for web applications, desktop applications and mobile phones, and living room devices.
OAuth2.0 has almost become a standard in today’s third-party platforms (I don’t know that 3.0 will be released in a few years). So since it is a standard, why can’t it be implemented with a relatively standard class library or project? Look through the entire open source projects in China, let alone C#, there are no such ready-made projects for Java and PHP, so I will just give up my old skills and continue to contribute my meager efforts to you.
Due to time constraints, I only made 6 interfaces in the first version. The callback address of WeChat is set on the public platform and does not support passing parameters. Please note that only register_third.aspx in the entire project needs to be connected with your membership system. , nothing else needs to be modified~~ Oh, I forgot to mention that appkey and appsecret need to be modified, you know.