You can use Xsolla Launcher to deliver your application to users and update it. The Launcher contains a built-in authorization tool. To avoid the need to re-enter username and password, set up authorization in your application via the Launcher.

Set up SDK and Launcher to work together

1. Set up Launcher in your Publisher Account.

2. Customize the launcher UI.

3. Implement the Launcher authorization logic in your application.
4. Generate a launcher installation file and a build archive.
5. Create an application build.
6. Upload the application build to the Xsolla update server.

Implement logic for authentication via Launcher

The flow for authorization in the application via Launcher is as follows:

1. The user is authorized in Launcher.
2. The user installs and runs the application.
3. Launcher runs the application and passes user parameters via the command line. The authorization token is passed in the xsolla-login-token parameter.
4. The application processes command line parameters and obtains a token. An example of a token processing script can be viewed in the demo project.
5. The application validates the received token. An example of a token validation script can be viewed in the demo project.
6. The application automatically authorizes the user without displaying an authorization page. An example of a user authorization script can be viewed in the demo project.

Create an application build

1. Go to your Unity project.
2. Click Window > Xsolla > Edit Settings in the main menu. In the Inspector panel:
   1. In the Project ID field, specify the Project ID found in Publisher Account > Project settings > Project ID.
   2. In the Login ID field, specify the Login ID found in Publisher Account > Launcher > General settings > Authentication.

3. Run the user authorization scene, where the token is processed.
4. Click File > Build settings in the main menu and then click Add Open Scenes. Make sure the authorization scene is added first in the list.
5. Click Build.
6. In the pop-up window, specify the path to the directory where the finished build will be placed.

Native authentication allows players to enter your application via the installed Steam application.

To set up native authentication:

1. Set up silent authentication via Steam in Publisher Account.
2. Configure your Unity project.
3. Configure processing of events.
4. Ensure authentication via Steam.

Configure your Unity project

1. Create a steam_appid.txt file and enter your application ID in Steam there. Then, place this file in the Assets/Plugins/Steamworks.NET/redist/ catalog of your project.

2. Open your Unity project.
3. In the main menu, go to Window > Xsolla > Demo Settings.
4. In the Inspector panel:
   1. Check the Use Steam authorization box.
   2. In the Steam App ID field, specify your application ID in Steam. The value should be the same as the value in the steam_appid.txt file.

Configure processing of events

To authenticate users via Steam, you should pass a session ticket to the SilentAuth method. For an example, see the SteamAuth.cs class of the demo project.

Ensure authentication via Steam

1. Create the build of your Unity project for a stand-alone platform or start a scene.
2. Launch Steam and log in.
3. Launch your application. If everything is correct, you will be logged into the applictaion automatically.