Silent authentication via publishing platform

Silent authentication allows users to log into you application without having to enter their credentials again. With this type of authentication, the Xsolla Login server uses the credentials that the user provided on the application’s publishing platform.

To implement silent authentication via the publishing platform:

1. Set up the application in the platform developer account.
2. Set up silent authentication in Publisher Account.
3. Complete integration steps on your application’s side.

Set up silent authentication

In the Login product, two approaches to enabling silent authentication are implemented:

• by configuring the classic login option (see instructions below);
• by creating a shadow Login project (see How to set up a shadow Login project).

To enable silent authentication in the classic login option:

1. Open your project in Publisher Account and go to the Login section.
2. Click Configure in the panel of a classic login option.
3. On the navigation page, 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. Repeat steps 4 – 6 for other publishing platforms, if required.

Integrate on application side

1. Integrate the publishing platform SDK into your application.
2. Implement the logic of obtaining the session ticket:

1. • For Steam, get the session ticket.
   • For Xbox Live, form a session ticket based on the platform data after user authentication. The parameter is formed based on the \-\;\ template where:
     • \ — Xbox User ID
     • \ — user hash
     • \ — Xbox Secure Token Service
   • For Epic Games, get the authorization code (exchange code) from the platform that is generated after user authentication and is used as a session ticket.

3. Implement user authentication logic using SDK methods:

1. • SilentAuth — exchanges the session ticket from the publishing platform to JSON Web Token (JWT) and authenticates the user.
   • OAuthLogout — ends the active user session.

Useful links