Skip to content

User Account Data Mapping ​

After integrating the OpenPaaS service, the game side will uniformly obtain the user's unique identifier from OpenPaaS. For user logins in legacy games, the APP needs to pass the original unique identifier through OpenPaaS to the game.

1. Passing the Unique User Identifier for Legacy Games ​

1.1 Running Legacy Game Packages ​

  • Legacy game packages are supported for loading and running via a local path or URL.
  • The user login flow and information retrieval remain consistent with the original flow; no additional handling is required.

1.2 Updating Legacy Game Packages to OpenPaaS ​

Because OpenPaaS provides a brand-new login solution, the resulting user identity (openid & unionid) differs from the user identity originally issued by the APP. When loading legacy games, OpenPaaS will additionally request the original identity from the APP:

  • After a legacy game is migrated to OpenPaaS, when a user logs into the game with the new version of the game package, OpenPaaS will call onGetLegacyUserIdentity to obtain the user identity originally issued by the APP.
  • When OpenPaaS calls onGetLegacyUserIdentity, the APP must return the user's original identity. OpenPaaS will then process it to form a new identifier and a mapping between the new and old identifiers, and return it to the game side. Each APP must return the actual identity originally issued to the game; otherwise, user data may be lost after the game is updated.
    • The original APP identity may be a single userid, or another field name such as openid.
    • If the original APP also issued an identity for the same user across multiple games, this must also be returned to OpenPaaS.

1.3 New Game User Login ​

  • For user logins in new games, OpenPaaS will directly generate the user identity based on the unique user identifier, APP information, and game information provided by the APP.