How to set up a shadow Login project

1. Create a shadow Login project if it has not already been created (see Integration Guide, steps 1–5).
2. Set up your shadow Login project in Publisher Account.
3. Integrate the solution on the side of your application.

Setting up in Publisher Account

1. Open your project in Publisher Account and go to the Login section.
2. Click Configure in the panel of a shadow Login project.
3. Go to the Authentication block and select the Publishing platforms section.

4. To connect a publishing platform, click the ⚙ icon next to its name and select Settings.

5. In the modal window, specify the parameters for the selected platform:
   • Steam:
     • Application ID — AppID of your account on the platform;
     • Application secret key — Web API Key.
   • Epic Games:
     • Application ID — Client ID of the client of your game on the platform;
     • Application secret key — Secret key of the client of your game on the platform.
   • Xbox Live:
     • Application ID — Application ID/Client ID of your game on the platform;
     • Application secret key — Application Secret generated when your game was registered on the platform.

6. Click Connect.
7. Go to the Callback URLs tab and specify the following parameters:
   • Callback URL — the URL or path in the application to which users are redirected after they have successfully authenticated, confirmed their email, or reset their password. You can specify multiple valid URLs.
   • Error callback URL — the URL or path in the application to which users are redirected in case of an authentication error. If no value is specified, the Callback URL value will be used.

8. Click Save changes.

Application side integration

Use the instruction for the publishing platform that hosts your application:

• Steam
• Xbox Live
• Epic Games

Steam

1. Get the session ticket.
2. Pass it to the silent authentication request (JWT or OAuth 2.0) as a session_ticket parameter.

Xbox Live

1. Form a session ticket (session_ticket parameter) based on the platform data after user authentication. The parameter is formed based on the <xid>-<uhs>;<XSTSToken> template where:
   • <xid> — Xbox User ID;
   • <uhs> — user hash;
   • <XSTSToken> — Xbox Secure Token Service.
2. Pass the session_ticket parameter to the silent authentication request (JWT or OAuth 2.0).

Epic Games

1. Get the exchangecode authorization code from the platform, which is generated after user authentication.
2. Pass the received exchangecode to the silent authentication request (JWT or OAuth 2.0) as the session_ticket parameter.

Rate this page

Is there anything we can improve? Send

Don’t want to answer

Thank you for your feedback!