OAuth 2.0 uses short-lived tokens with long-term authorization (refresh tokens) instead of long-lived tokens. A refresh token allows users to stay in your application for an extended period of time without needing to re-enter their username and password. This eliminates the risk of compromising user authentication data.

Set up OAuth 2.0 for authorization:

• via username or email and password
• via social networks
• via Steam

If the option is enabled, user registration and authentication is carried out by calling the Register new user and JWT auth by username and password API calls. The SDK provides the same methods for OAuth 2.0 authorization as for JWT token authorization.

To configure OAuth 2.0 authorization:

1. Set up OAuth 2.0 authentication for Login project in your Publisher Account.
2. Set up asset in your Unity project.

Set up OAuth 2.0 authentication for Login project in your Publisher Account

1. Go to your Publisher Account.
2. Click Login in the side menu.
3. Click Configure in the Login project pane.
4. Go to the Security block and select the OAuth 2.0 section.
5. Click Add OAuth 2.0.
6. In the OAuth 2.0 redirect URIs field, specify the URL or path in the application to which users are redirected after they have successfully authenticated, confirmed their email, or reset their password.
7. Click Connect.
8. Copy and save the Client ID.

Set up asset in your Unity project

1. Go to your Unity project.
2. Click Window > Xsolla > Edit Settings in the main menu.
3. In Inspector panel:
   1. In the Authorization Type field, select OAuth2.0.
   2. In the OAuth2.0 client ID field, specify Client ID received when setting up OAuth 2.0 in Publisher Account.

The following methods are implemented in the SDK to work with refresh tokens:

• RefreshOAuthToken — refreshes the existing token using previously saved OAuth2.0 refresh token.
• ExchangeCodeToToken — exchanges the user’s authentication code for a valid JWT.

The oauthState argument found in the GetSocialNetworkAuthUrl method is used for additional user verification during OAuth 2.0 authentication. This argument is used to mitigate possible CSRF attacks.

Token invalidation allows for improved security of user authentication data in your application. If the option is enabled, a new token replaces the old one that becomes invalid every time the user authenticates.

When using SDK, invalidation of the existing token and generation of a new one is made by calling Auth by username and password and Auth via social network API calls, if the with_logout parameter is set to 1.

To enable token invalidation in your Unity project:

1. In the main menu, go to Window > Xsolla > Edit Settings.
2. Go to the Inspector panel. In the Authorizaton Type field, select JWT. Check the Invalidate Existing Sessions box.