Just found this out of the blue. . But there seems to be no good solution. Ask a question about QQ Internet login: Unify users between multiple applications under one developer account
5.12 supplement
I found two methods on the Internet:
The pitfall of creating applications on Tencent’s open platform, how can multiple applications share the same Appid? This method is suitable for applications that have not yet been launched. There is no user data that needs to be migrated, and it can be used for personal testing.
When using QQ third-party login, the openid obtained by the mobile application and the website application are different for the same QQ number. This method is suitable for applications that are already in the production environment and have been trapped. User account data needs to be merged. I haven't tested this method.
You cannot unify users by relying on third-party login, you must have a unique credential. Usually it is an email or mobile phone number. You can register directly by binding the mobile phone number or email, or you can first log in through a third party and then let the user bind the mobile phone number or email (the advantage of this is that the user does not need to fill in the nickname and avatar) )
When the first entrance comes in, a user ID is assigned internally, and then the subsequent ones are related. Add a correlation table and it will be KO
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Just found this out of the blue. . But there seems to be no good solution.
Ask a question about QQ Internet login: Unify users between multiple applications under one developer account
5.12 supplement
I found two methods on the Internet:
The pitfall of creating applications on Tencent’s open platform, how can multiple applications share the same Appid? This method is suitable for applications that have not yet been launched. There is no user data that needs to be migrated, and it can be used for personal testing.
When using QQ third-party login, the openid obtained by the mobile application and the website application are different for the same QQ number. This method is suitable for applications that are already in the production environment and have been trapped. User account data needs to be merged. I haven't tested this method.
After logging in with QQ, let him bind WeChat... and the two open_ids will be associated...
Third-party login is just a way to attract traffic. Let him bind his cell phone.
You cannot unify users by relying on third-party login, you must have a unique credential. Usually it is an email or mobile phone number. You can register directly by binding the mobile phone number or email, or you can first log in through a third party and then let the user bind the mobile phone number or email (the advantage of this is that the user does not need to fill in the nickname and avatar) )
When the first entrance comes in, a user ID is assigned internally, and then the subsequent ones are related. Add a correlation table and it will be KO
Github does not have such a thing as openid, but it will return the user's id. You can use that id as openid, which is the user's unique identifier.
QQ is really difficult to do. If it doesn’t work, you can only get a main account and then bind it with a third party.