


Ask a question about QQ Internet login: Unify users between multiple applications under one developer account
Jul 06, 2016 pm 01:53 PM
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 openid
s). Then when he is in B
When 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.
Reply content:
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 openid
s). Then when he is in B
When 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. .

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

In PHP, you can use square brackets or curly braces to obtain string specific index characters, but square brackets are recommended; the index starts from 0, and the access outside the range returns a null value and cannot be assigned a value; mb_substr is required to handle multi-byte characters. For example: $str="hello";echo$str[0]; output h; and Chinese characters such as mb_substr($str,1,1) need to obtain the correct result; in actual applications, the length of the string should be checked before looping, dynamic strings need to be verified for validity, and multilingual projects recommend using multi-byte security functions uniformly.

AgeneratorinPHPisamemory-efficientwaytoiterateoverlargedatasetsbyyieldingvaluesoneatatimeinsteadofreturningthemallatonce.1.Generatorsusetheyieldkeywordtoproducevaluesondemand,reducingmemoryusage.2.Theyareusefulforhandlingbigloops,readinglargefiles,or

To prevent session hijacking in PHP, the following measures need to be taken: 1. Use HTTPS to encrypt the transmission and set session.cookie_secure=1 in php.ini; 2. Set the security cookie attributes, including httponly, secure and samesite; 3. Call session_regenerate_id(true) when the user logs in or permissions change to change to change the SessionID; 4. Limit the Session life cycle, reasonably configure gc_maxlifetime and record the user's activity time; 5. Prohibit exposing the SessionID to the URL, and set session.use_only

You can use substr() or mb_substr() to get the first N characters in PHP. The specific steps are as follows: 1. Use substr($string,0,N) to intercept the first N characters, which is suitable for ASCII characters and is simple and efficient; 2. When processing multi-byte characters (such as Chinese), mb_substr($string,0,N,'UTF-8'), and ensure that mbstring extension is enabled; 3. If the string contains HTML or whitespace characters, you should first use strip_tags() to remove the tags and trim() to clean the spaces, and then intercept them to ensure the results are clean.

The urlencode() function is used to encode strings into URL-safe formats, where non-alphanumeric characters (except -, _, and .) are replaced with a percent sign followed by a two-digit hexadecimal number. For example, spaces are converted to signs, exclamation marks are converted to!, and Chinese characters are converted to their UTF-8 encoding form. When using, only the parameter values ??should be encoded, not the entire URL, to avoid damaging the URL structure. For other parts of the URL, such as path segments, the rawurlencode() function should be used, which converts the space to . When processing array parameters, you can use http_build_query() to automatically encode, or manually call urlencode() on each value to ensure safe transfer of data. just

There are two main ways to get the last N characters of a string in PHP: 1. Use the substr() function to intercept through the negative starting position, which is suitable for single-byte characters; 2. Use the mb_substr() function to support multilingual and UTF-8 encoding to avoid truncating non-English characters; 3. Optionally determine whether the string length is sufficient to handle boundary situations; 4. It is not recommended to use strrev() substr() combination method because it is not safe and inefficient for multi-byte characters.

To set and get session variables in PHP, you must first always call session_start() at the top of the script to start the session. 1. When setting session variables, use $_SESSION hyperglobal array to assign values ??to specific keys, such as $_SESSION['username']='john_doe'; it can store strings, numbers, arrays and even objects, but avoid storing too much data to avoid affecting performance. 2. When obtaining session variables, you need to call session_start() first, and then access the $_SESSION array through the key, such as echo$_SESSION['username']; it is recommended to use isset() to check whether the variable exists to avoid errors

Key methods to prevent SQL injection in PHP include: 1. Use preprocessing statements (such as PDO or MySQLi) to separate SQL code and data; 2. Turn off simulated preprocessing mode to ensure true preprocessing; 3. Filter and verify user input, such as using is_numeric() and filter_var(); 4. Avoid directly splicing SQL strings and use parameter binding instead; 5. Turn off error display in the production environment and record error logs. These measures comprehensively prevent the risk of SQL injection from mechanisms and details.
