Skip to content

Overview ​

The server is involved in data encryption and decryption at several key steps of the complete OpenPaaS service flow. Each is described below.

1. Key Steps ​

The key steps involving the server are as follows:

  • User Signature (userSignature): Before the SDK authentication call, it is generated by the APP server and issued to the APP, to be used as an input parameter for SDK authentication.
  • Session Key (sessionKey): Generated by SUD OP SVR. It is issued to and held by the Game SVR when the player logs into the game; when retrieving sensitive user information, the APP SVR temporarily obtains this key to encrypt the sensitive data, and after the Game SVR receives the encrypted data, it decrypts it using the sessionKey it holds.
  • API Security Keys (symmetric key / app key pair / SUD OpenPaaS certificate): Used for S2S interface communication between the APP server and SUD OP SVR. See Server API Signature and Encryption for details.

See the Key Description document for the complete description of each type of key.

2. Flow Description ​

Participants ​

  • APP: The app client
  • SUD OP: The communication middleware integrated into the client
  • Game: The game client
  • Game SVR: The game's server
  • SUD OP SVR: SUD's server (the core hub for credential flow and verification)
  • APP SVR: The app's server

1. Before SDK authentication, the APP obtains the userSignature from the APP server ​

2. After the player logs into the game, the Game SVR decrypts sensitive user information using the session key ​

  • Login stage: When the player logs into the game, SUD OP SVR generates the sessionKey for the current session and issues it to the Game SVR to hold. It is kept only on the server side and is not delivered to the client.
  • When retrieving sensitive information: SUD OP SVR encrypts the sessionKey into encrypted_session_key, which is relayed via SUD OP → APP to the APP SVR; the APP SVR decrypts it with the data symmetric encryption key to obtain the sessionKey and AES-encrypts the sensitive user information.
  • The encrypted result userinfo / encryptedData / iv / signature is returned along the original path to the Game, where the Game SVR decrypts the sensitive data using the sessionKey it already held from the login stage (see the linked document below for the integrity check and signature algorithm).
  • Session Key Decryption Guide
  • Full Flow for a Game Retrieving User Information

3. The APP server uses API security keys when communicating with SUD OP SVR via S2S API ​

3. FAQ ​