I used the WeChat official account to log in, and then I learned that the WeChat open platform has a unionid. As long as the developer binds his own official account or other applications, then for the same WeChat user, under the current developer account The unionid are the same, which is helpful for unifying accounts when developers have multiple applications.
For example: I have A，B two public accounts, a mobile application C, and a web application D. Four applications will have four appid. When a WeChat user enters A If you log in with authorization, there will be a unique A relative to appid's openid (Similarly, when B，C，D is authorized, there will be three other different openids). Then when he is in BWhen authorizing, the previous A account will no longer be recognized. This will not achieve the effect of unifying my users, because A,B is all mine.
Now with unionid, this problem is solved. When authorizing, in addition to returning openid, unionid will also be returned. Based on this, we can judge that this WeChat user has been authorized using A before. Then it will be recognized and there is no need to ask B to authorize it again, just let it log in directly. This achieves the effect of unifying accounts when I have multiple applications.
Hehe~ WeChat’s solution is excellent.
Then I looked at the QQ login and found that there was no such thing unionid.
So I looked at other open platforms, Renren, Sina Weibo, these authorizations are not returned openid, but will get their real UID. In this way, there will not be multiple applications under one developer account. It's a matter of unification.
My current question:
1: Why do WeChat and QQ use openid instead of real uid like Weibo? Instead of digging a hole yourself?
2: Although WeChat and QQ used openid to dig holes, why did the WeChat open platform use unionid to fill this hole, but QQ Internet did not?
3: QQ Internet dug a hole but failed to fill it, so how do we solve this problem and open up the authorization interoperability of multiple applications under one developer account?
Supplement: In fact, the principle of login authorization and binding authorization is to associate the “uid” (quotation marks here) returned by the third-party platform after authorization with our own uid to achieve the purpose of binding, but QQ, WeChat, unlike Weibo, returns openid, so there is a problem with this post.
Attached are several related links:
http://mp.weixin.qq.com/wiki/4/9ac2e7b1f1d22e9e57260f6553822520.html
http://wiki.connect.qq.com/Get user openid_oauth2- 0
http://wiki.open.qq.com/wiki/API3.0 Document
http://open.weibo.com/wiki/Oauth2/access_token
The above is my superficial understanding. After all, my practical experience is not strong yet. I hope experienced experts can criticize and correct me. Thank you.
I used the WeChat official account to log in, and then I learned that the WeChat open platform has a unionid. As long as the developer binds his own official account or other applications, then for the same WeChat user, under the current developer account The unionid are the same, which is helpful for unifying accounts when developers have multiple applications.
For example: I have A，B two public accounts, a mobile application C, and a web application D. Four applications will have four appid. When a WeChat user enters A If you log in with authorization, there will be a unique A relative to appid's openid (Similarly, when B，C，D is authorized, there will be three other different openids). Then when he is in BWhen authorizing, the previous A account will no longer be recognized. This will not achieve the effect of unifying my users, because A,B is all mine.
Now with unionid, this problem is solved. When authorizing, in addition to returning openid, unionid will also be returned. Based on this, we can determine that this WeChat user has been authorized using A before. Then it will be recognized and there is no need to ask B to authorize it again, just let it log in directly. This achieves the effect of unifying accounts when I have multiple applications.
Hehe~ WeChat’s solution is excellent.
Then I looked at the QQ login and found that there was no such thing unionid.
So I looked at other open platforms, Renren, Sina Weibo, these authorizations are not returned openid, but will get their real UID. In this way, there will not be multiple applications under one developer account. It's a matter of unification.
My current question:
1: Why do WeChat and QQ use openid instead of real uid like Weibo? Instead of digging a hole yourself?
2: Although WeChat and QQ used openid to dig holes, why did the WeChat open platform use unionid to fill this hole, but QQ Internet did not?
3: QQ Internet dug a hole but failed to fill it, so how do we solve this problem and open up the authorization interoperability of multiple applications under one developer account?
Supplement: In fact, the principle of login authorization and binding authorization is to associate the “uid” (quotation marks here) returned by the third-party platform after authorization with our own uid to achieve the purpose of binding, but QQ, WeChat, unlike Weibo, returns openid, so there is a problem with this post.
Attached are several related links:
http://mp.weixin.qq.com/wiki/4/9ac2e7b1f1d22e9e57260f6553822520.html
http://wiki.connect.qq.com/Get user openid_oauth2- 0
http://wiki.open.qq.com/wiki/API3.0 Document
http://open.weibo.com/wiki/Oauth2/access_token
The above is my superficial understanding. After all, my practical experience is not strong yet. I hope experienced experts can criticize and correct me. Thank you.
Since the supplier’s API does not provide the effect we need, there is nothing we can do, and we cannot fake it on this issue.
After all, the value of openid is unique and is generated and verified instantly. It is impossible to pass a common openid to all four applications.
Back to your question:
1. "Why does Weibo have no pitfalls but QQ has pitfalls?"
No reason, Sina programmers designed to return uid, while QQ WeChat designed 2 to return openid
2. “WeChat fills in the gaps but QQ doesn’t”
The two product teams are different, there is no inevitability. I haven’t used the WeChat open platform for a long time. I don’t know when unionid appeared. If it appeared recently, then I believe qq will soon fill the gap
3. "How does QQ solve multi-application interoperability"
There should be no solution after just a few minutes of thinking. Since qq requires openid for verification, and this openid is even generated, there should be no solution.
Of course, the specific situation depends on their documentation
My humble opinion
The id of qq is the qq number. In order to prevent the user’s personal information from being obtained through other channels through id
Guess. .
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
