MSDK-V3 Login State Collection
The APP integrated with MSDK V3 version can select [MSDK v3] in the login verification of the survey settings. When users submit the survey, the survey system will automatically obtain the MSDK login status and store it in the response data.
MSDK-V3 Login State Encryption and Decryption Instructions
The survey system backend is used to decrypt and obtain the player's login status process. The game side only needs to focus on whether the correct login status parameters are injected after the survey link.
The game client obtains the login state encrypted token
The game client needs to encrypt the survey link and inject login status information through the "Get Encrypted Ticket" interface provided by the MSDK webview; parameters include: msdkEncodeParam, timestamp, appid, algorithm, version, sig, encode, etc.
MSDK Documentation Reference: [Get Encrypted Ticket]
https://wiki.ssl.msdk.qq.com/Android/webview.html#Android_UrlAddEncodeParam
Survey system decrypts and retrieves login status information
The system obtains the plaintext openid decrypted from msdkEncodeParam through the "decryption verification" interface, and the game side does not need to pay attention.
MSDK Document Reference: [Decryption Verification]
https://wiki.ssl.msdk.qq.com/Android/webview.html#Android_DecodeLoginInfo
(1) The system prioritizes using the msdkEncodeParam parameters for login state decryption. In this case, it is required to include the following six parameters: timestamp, appid, algorithm, version, sig, and encode. An example is as follows:
(2) When the msdkEncodeParam parameter cannot decrypt the login state properly, the system will directly use the openid parameter value as the login state.
(3) To obtain custom parameters, you can append "info" to the link to store custom content in the survey data (optional).
Login Failure Notice
When the system fails to obtain the correct login status, a warning pop-up will be displayed. The main reasons for the failure are as follows:
(1) When decrypting the login state with msdkEncodeParam, the decryption failed due to missing parameters such as timestamp, appid, algorithm, version, sig, and encode.
(2) The openid parameter is missing in the link, resulting in the inability to obtain the login status.
(3) The survey link with the login state parameters injected is too long, causing some parameters to be truncated and missing (requires separate handling by the client).
If the MSDK-V3 login state collection interface fails to integrate, you can use the parameter passing (strict verification mode, non-verification mode) interface to achieve login state transmission.
最后更新于
这有帮助吗？