Ask a question about qq internet login: uniform user between multiple applications under a developer account

I have used a public account to log on and know that the open platform has a unionid. as long as the developer binds his/her own public account or other applications, for the same user, the unionid under the current developer account is the same, which is beneficial when the developer has multiple applications... I used a public account to log on, and then I learned that there is an open platform unionidAs long as the developer binds his/her own public account or other applications unionidIs the same. this helps developers to have a unified account when they have multiple applications.

For example, I haveA，BTwo public accounts and one mobile appC, Web applicationDFour applications have fourappidWhen a userAUnder the authorization login, there will beAOfappidA uniqueopenid(LikewiseB，C，DThe other three are different during authorization.openid) Then when heBBefore authorizationAIn this way, the effect of my unified user is not achieved, becauseA,BIt's all mine.

Now we haveunionidThen this problem is solved. in addition toopenidWill returnunionidThen, you can determine that the user usedAIf you have been authorized, you can identify it without having to make it happen again.BAuthorize it once so that it can log on directly. In this way, I have multiple applications with a unified account.

Ah ~ This solution is excellent.

Then I saw the QQ login and found that there was no suchunionid.

So I read other open platforms, such as Renren and Sina Weibo. These authorizations are not returned.openidBut will get their realUIDIn this way, there will be no inconsistency between multiple applications under a developer account.

My current problems:

1: Why, qq, useopenidInstead of using real content like WeibouidWhat about it? But do you have to dig a hole yourself?

2: qqopenidWhy open the platformunionidI entered this pitfall, but qq is not connected?

3?

Supplement: in fact, for logon authorization, the binding authorization principle is to obtain the returned information from a third-party platform after authorization.“uid”(Quotes here) with our ownuidIn order to achieve the purpose of binding, qq, unlike Weibo, returnsopenid.

Link:
Http://mp.weixin.qq.com/wiki/4/9ac2e7b1f1d22e9e57260f6553822520.html
Http://wiki.connect.qq.com/the user openid_oauth2-0 is selected.
Http://wiki.open.qq.com/wiki/api3.0documentation
Http://open.weibo.com/wiki/Oauth2/access_token

The above is my simple understanding. after all, my practical experience is not strong. I hope that experienced experts will criticize and correct me. thank you.

Reply content:

I used a public account to log on, and then I learned that there is an open platformunionidAs long as the developer binds his/her own public account or other applicationsunionidIs the same. this helps developers to have a unified account when they have multiple applications.

For example, I haveA，BTwo public accounts and one mobile appC, Web applicationDFour applications have fourappidWhen a userAUnder the authorization login, there will beAOfappidA uniqueopenid(LikewiseB，C，DThe other three are different during authorization.openid) Then when heBBefore authorizationAIn this way, the effect of my unified user is not achieved, becauseA,BIt's all mine.

Now we haveunionidThen this problem is solved. in addition toopenidWill returnunionidThen, you can determine that the user usedAIf you have been authorized, you can identify it without having to make it happen again.BAuthorize it once so that it can log on directly. In this way, I have multiple applications with a unified account.

Ah ~ This solution is excellent.

Then I saw the QQ login and found that there was no suchunionid.

So I read other open platforms, such as Renren and Sina Weibo. These authorizations are not returned.openidBut will get their realUIDIn this way, there will be no inconsistency between multiple applications under a developer account.

My current problems:

1: Why, qq, useopenidInstead of using real content like WeibouidWhat about it? But do you have to dig a hole yourself?

2: qqopenidWhy open the platformunionidI entered this pitfall, but qq is not connected?

3?

Supplement: in fact, for logon authorization, the binding authorization principle is to obtain the returned information from a third-party platform after authorization.“uid”(Quotes here) with our ownuidIn order to achieve the purpose of binding, qq, unlike Weibo, returnsopenid.

Link:
Http://mp.weixin.qq.com/wiki/4/9ac2e7b1f1d22e9e57260f6553822520.html
Http://wiki.connect.qq.com/the user openid_oauth2-0 is selected.
Http://wiki.open.qq.com/wiki/api3.0documentation
Http://open.weibo.com/wiki/Oauth2/access_token

The above is my simple understanding. after all, my practical experience is not strong. I hope that experienced experts will criticize and correct me. thank you.

Since the supplier's API does not provide the results we need, there is no way to do it, and we cannot forge it on this issue.
After all, the value of openid is unique and generated and verified in real time. a common openid cannot be passed to all four applications.
Back to your question:
1. "Why are there any pitfalls in Weibo and qq"

No, Sina's programmers designed the return uid, while qq designed 2 to return the openid.

2. "fill in and QQ does not"

The two product teams are different and there is no inevitability. I haven't used the open platform for a long time. I don't know when unionid appears. If it appears recently, I believe qq will soon be filled in.

3. "How qq solves multi-application intercommunication"

There is no solution to the current several minutes of thinking. since qq requires openid for verification, even if this openid is generated, there should be no way.

Of course, you should also read their documents for details.

Humble Opinion

The qq id is the qq number. to prevent the user's personal information from being obtained through other channels

Guess ..