Set up Device ID as an identity provider

Last updated on August 5, 2026

Overview​

A Device ID is a unique identifier for a device. With AccelByte Gaming Services (AGS), your player can use their Device ID to log in to your game and give them a headless account. Read the getting online tutorials for Unreal Engine and Unity to learn how to integrate a Device ID login method into your game.

Goals​

  • Enable Device ID authentication for your game using the AGS SDK.

Prerequisites​

  • An AGS Admin Portal account with permissions to manage authentication.
  • A game namespace.

Set up the Device ID login provider in AGS​

  1. In the AGS Admin Portal, go to your game namespace.

  2. On the sidebar menu, go to Foundations > 3rd Party Integrations > Auth & Account Linking.

  3. On the Auth & Account Linking page, click + Add New.

    Auth & Account Linking page with the Add New button highlighted

  4. On the Select login provider page, find Device ID under the Device tab and click on it.

    Device tab selected on the Select login provider page showing the Device ID card

  5. The Set Up Device login provider form appears.

    Set up Device ID login provider form with Platform ID and Redirect URI fields

  6. Fill in the following fields:

    • Platform ID: device. Set automatically. Cannot be changed.
    • Redirect URI: The OAuth callback URL. Defaults to http://127.0.0.1.

  7. Click Add & Activate to create and activate the provider in one step. Alternatively, click Add to create without activating.

Edit a login provider​

  1. On the Auth & Account Linking page, click the Device ID provider.

  2. The Device login provider dialog appears. Update the fields as needed.

  3. Use the Status toggle at the top to activate or deactivate the provider.

    Device login provider configuration dialog with Status toggle and Redirect URI field

  4. Click Save.

Best practice​

Since your users don't need to input any credentials as they will be using a device to log in, there's a risk a user will lose access to their device and it will be difficult to recover their account. To mitigate this risk, we suggest you prompt your users to upgrade their headless account to a full account. For more details about accounts, you can read the documentation on how accounts work.

Last updated on
On this page