An example of the authorization page when the scope parameter is equal to the snsapi_userinfo is as follows: If the user gives authorization permission, the page redirects to redirect_uri/? Otherwise, only the state parameter is included in the URL, such as redirect_uri? Code description: The code is the certificate for obtaining the access token and is therefore different for each authorization.
Two links are provided below for your reference (please open them in your We Chat client) Scope = snsapi_base https://open.com/connect/oauth2/authorize? d=&c=wx Adapter&m=mobile Deal&showwxpaytitle=1&vb2ctag=4_2030_5_1194_60&response_type=code&scope=snsapi_base&state=123#wechat_redirect Scope = snsapi_userinfo https://open.com/connect/oauth2/authorize?
appid=wxf0e81c3bee622d60&redirect_uri= App authorization scope. snsapi_base: No authorization page is prompted, redirect occurs, and only the user Open ID can be obtained.
Note that the access token here for web authorization obtained by the code is not the one mentioned in the Basis Support pages.
If the scope parameter is snsapi_base, both access token and Open ID are obtained in this step.
The Economist chimed in and highlighted a ‘Galapagos Island’ effect in the development of the technology ecosystems of China and the West.
While each positioned it as “going back in time” when you go from using We Chat to a Western messaging platform, the reality is both ecosystems are bustling with innovation and can serve as inspiration for each other.
snsapi_userinfo: prompts the authorization page, enabling you to obtain a user's nickname, gender and city via the Open ID.
For a non-follower, you can also obtain information if the user gives permission.
It's an all-in-one experience for keeping in touch with people you know: You can use it to place voice calls, send text messages, share stickers, play games, and more.