Skip to content

Web login

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

When you wish to use blockchain login

  1. 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.

  2. 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.

  3. Setting up Web Login in Authentication

    • 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 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.”

  4. API

Note

An account conflict occurs when a PlayerID has already been created via initial IdP linking through web login, and the user then logs into a game with the Hive SDK and tries to link an additional IdP from the game profile. Since the PlayerID already exists from the web login, the user is prompted to choose which account to use.

When you wish to use login in your community or website

  1. Summary

    • Web Login generates the user identifier (User ID) within the product during the initial IdP linkage to prevent account conflicts from Web Login v1.
    • Web Login 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.

  2. 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.

  3. Set up Web Login in Authentication

    • 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 Registration Option: Mark membership as “enabled”.

  4. API

Set up the IdP console

If you configured Web Login in Authentication > Auth Settings > Login Settings, you must register the Web Login Redirect URI in the respective IdP consoles such as Google or Apple.

Google

Warning

If withhive.com is automatically listed under Authorized Domains on the OAuth consent screen in the Google Cloud Console, do not add sensitive or restricted scopes. Hive does not provide domain ownership for withhive.com.

Facebook

Apple