Skip to content

Web login

Web login is a product that enables secure and convenient login across various websites, communities, and blockchain.

Web login type

There are two types of Web Login: Web Login v1 and Web Login v2, each with different operation methods.

When you wish to use blockchain login

  • Summary

    • Generate PlayerID, the user identifier, in the web login during the initial IdP linkage.
    • This is used for login processing in the blockchain. Initial IdP linkage should only be done within the game to avoid account conflicts. Additionally, the login screen will be displayed in the blockchain after SMS verification.
    • This is used when you wish to handle login only on the web and use the user identifier as PlayerID for a game that does not implement the Hive SDK.

  • Create AppID in App Center

    • You need to create an AppID in App Center to enable web login. Please refer to the AppID Registration Guide in App Center for details.

  • Setting up Login in Web Login v1 App Center

    • After creating an AppID, configure the login settings as follows. Web Login doesn’t provide guest login.
      • Registering Login Key to Use
      • Registering Redirect URIs: Enter the page addresses where users will be redirected after completing Web Login. You can register up to 5 addresses. If you want to use both “http://” and “https://” versions, enter the domain (e.g., www.a.com) as the URI.
      • Membership V4 Registration Option: If membership registration is marked as “enabled,” the initial IdP linkage is available through Web Login, but it may cause account conflicts. If membership registration is marked as “disabled,” the initial IdP linkage can only be done through the game. XPLA GAMES marks membership registration as “disabled.”

  • API

    • Web Login v1 is an API utilized when you wish to use the login in the blockchain. Please refer to the API guide below to implement the Web Login v1 API.
Note
  • When utilizing Web Login v1, if a PlayerID is initially generated through IdP linkage and later a game with Hive SDK applies a guest login, attempting to connect additional IdPs in the game profile may lead to an account conflict. This occurs because the PlayerID was already generated through Web Login, prompting the user to choose an account.

When you wish to use login in your community or website

  • Summary
    • Web Login v2 generates the user identifier (User ID) within the product during the initial IdP linkage to prevent account conflicts from Web Login v1.
    • Web Login v2 generates the user identifier within the product, allowing it to be used in various situations without account conflicts. Use the Server API to link a PlayerID generated from the game.
  • Create AppID in App Center
    • You need to create an AppID in App Center to enable web login. Please refer to the AppID Registration Guide in App Center for details.
  • Set up Web Login v2 in App Center
    • After creating an AppID, configure the login settings as follows. Web Login doesn’t provide guest login.
      • Register Login Key to Use
      • Registering Redirect URIs: Enter the page addresses where users will be redirected after completing Web Login. You can register up to 5 addresses. If you want to use both “http://” and “https://” versions, enter the domain (e.g., www.a.com) as the URI.
      • Membership V4 Registration Option: Mark membership as “enabled”.
  • API

Set up the IdP console