External Provider Linking

PreviousConnect Identiy Provider to Player NextTransition from Guest Login to Other Provider

Last updated 1 day ago

External Provider Linking

In this How-to, we will link an existing Steam Account with a new Epic Games Account using authentication through auth.game.

The overall flow is as follows:

The player starts the linking process in the game client.
The game client redirects the player to the LootLocker authentication website (auth.game).
The player signs in with the provider they want add to their account.
The game client polls the server to check if the player has completed the web flow yet.
Once the player has completed the web flow, the game client links the new provider to the existing account.

Prerequisites

Before we begin, ensure you have the following:

Start Link Flow

We start in the game client, where we initiate the link flow. This will generate a URL that the player can use to authenticate with the provider.

Specific reference for providers are here:

curl --location --request POST 'https://api.lootlocker.com/game/session/remote/link/lease' \
    --header 'x-session-token: your_token_here' \
    --header 'Content-Type: application/json' \
    --data-raw '{
        "game_key": "your_api_key_here",
        "game_version": "1.0.0.0"
    }'

Poll for Link Status

While the player is authenticating with the provider, we need to poll the server to check if the player has completed the web flow yet. We recommend a polling interval of 2-3 seconds.

Specific reference for providers are here:

curl --location --request POST 'https://api.lootlocker.com/game/session/remote/link/lease' \
    --header 'x-session-token: your_token_here' \
    --header 'Content-Type: application/json' \
    --data-raw '{
        "game_key": "your_api_key_here",
        "game_version": "1.0.0.0"
    }'

Handle Link Results

Once the player has completed the web flow, the endpoint we have been polling will return a success response with a LootLocker session.

We have 2 main scenarios here:

The provider they authenticated with does not exist on another LootLocker account
The provider they authenticated with already exists on another LootLocker account

Depending on the scenario, we will need to handle the response differently.

In the following exameple, we will handle the first scenario, where the provider does not exist on another LootLocker account.

Specific reference for providers are here:

The provider name will be returned in the poll response.

    curl --location --request PUT 'https://api.lootlocker.io/game/v1/connected-accounts/transfer-providers' \
    --header 'Content-Type: application/json' \
    --data-raw '{
        "source_token": "session_token_from_game_client_here",
        "target_token": "session_token_from_poll_response_here",
        "identitiy_providers": [
            "provider_name_here",
        ]
    }'

In the second scenario, where the provider already exists on another LootLocker account, we will need to handle the flow differently.

The steps for moving the provider to the new account are the same as above, but we need to ensure the player understands that they are moving the provider to a different account, and that they might lose access to the old account.

In some games, you might even want to migrate some data from the old account to the new account.

This is a more complex flow, and we recommend reaching out to us for help with this.

PreviousConnect Identiy Provider to Player NextTransition from Guest Login to Other Provider

Last updated 1 day ago

In this How-to, we will link an existing Steam Account with a new Epic Games Account using authentication through auth.game.

The overall flow is as follows:

The player starts the linking process in the game client.
The game client redirects the player to the LootLocker authentication website (auth.game).
The player signs in with the provider they want add to their account.
The game client polls the server to check if the player has completed the web flow yet.
Once the player has completed the web flow, the game client links the new provider to the existing account.

Prerequisites

Before we begin, ensure you have the following:

Start Link Flow

We start in the game client, where we initiate the link flow. This will generate a URL that the player can use to authenticate with the provider.

Specific reference for providers are here:

curl --location --request POST 'https://api.lootlocker.com/game/session/remote/link/lease' \
    --header 'x-session-token: your_token_here' \
    --header 'Content-Type: application/json' \
    --data-raw '{
        "game_key": "your_api_key_here",
        "game_version": "1.0.0.0"
    }'

Poll for Link Status

While the player is authenticating with the provider, we need to poll the server to check if the player has completed the web flow yet. We recommend a polling interval of 2-3 seconds.

Specific reference for providers are here:

curl --location --request POST 'https://api.lootlocker.com/game/session/remote/link/lease' \
    --header 'x-session-token: your_token_here' \
    --header 'Content-Type: application/json' \
    --data-raw '{
        "game_key": "your_api_key_here",
        "game_version": "1.0.0.0"
    }'

Handle Link Results

Once the player has completed the web flow, the endpoint we have been polling will return a success response with a LootLocker session.

We have 2 main scenarios here:

The provider they authenticated with does not exist on another LootLocker account
The provider they authenticated with already exists on another LootLocker account

Depending on the scenario, we will need to handle the response differently.

In the following exameple, we will handle the first scenario, where the provider does not exist on another LootLocker account.

Specific reference for providers are here:

The provider name will be returned in the poll response.

    curl --location --request PUT 'https://api.lootlocker.io/game/v1/connected-accounts/transfer-providers' \
    --header 'Content-Type: application/json' \
    --data-raw '{
        "source_token": "session_token_from_game_client_here",
        "target_token": "session_token_from_poll_response_here",
        "identitiy_providers": [
            "provider_name_here",
        ]
    }'

In the second scenario, where the provider already exists on another LootLocker account, we will need to handle the flow differently.

In some games, you might even want to migrate some data from the old account to the new account.

This is a more complex flow, and we recommend reaching out to us for help with this.