> ## Documentation Index
> Fetch the complete documentation index at: https://devdocs.xbox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reference XBOX Game Streaming servers in XSTS claims

> Configure the Device capabilities (dca) claim in Partner Center and interpret it server-side to detect XBOX Game Streaming servers from an XSTS token.

In certain scenarios, your game may need to specifically reference and identify which users are coming from XBOX Game Streaming servers.

To do this, the following steps should be taken in Partner Center:

1. Within Partner Center, navigate to the applicable Relying Party and select the appropriate claim found in [XBOX services security token claims (microsoft.com) (NDA topic)](/services/xbox-services/fundamentals/s2s-auth-calls/service-authentication/security-tokens/live-token-claims). To understand which claim to use and what value is expected, look for the term "XBOX Game Streaming server" in the linked claims documentation.
2. Update Claim schema to include the appropriate variable referencing XBOX Game Streaming.
3. Return to the main 'Relying Parties' menu and click 'Publish'.

<Note>Adjustments to an existing relying party will require a device and title restart (to clear the console cache) in order to get newly minted XSTS tokens (or wait for a period of about 4 hours for the previous one to expire).</Note>

## Detect an XBOX Game Streaming server from the Device capabilities (`dca`) claim

After you configure your relying party to include the Device capabilities claim, your service can inspect the `dca` value inside the `xdi` (device identity) section of the decrypted XSTS token to determine whether the token was minted on an XBOX Game Streaming server.

The `dca` claim is an integer array. Interpret it as follows:

| `dca` value                  | Meaning                                                                                                                                                                                                                                                                       |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `2`, `1 2`, or `2 1`         | The device is an XBOX Game Streaming server (with or without an ODD). Treat it as a cloud instance.                                                                                                                                                                           |
| `1` or no value              | The device is XBOX console hardware (with or without an ODD). Treat it as a non-streaming device.                                                                                                                                                                             |
| Claim omitted from the token | The relying party is not configured to emit `dca`, or the token came from a client that does not emit device identity claims (for example, non-XBOX platforms). Treat absence as a non-streaming device only after you confirm the relying party emits `dca` for XBOX tokens. |

Because an omitted claim is indistinguishable from a misconfigured relying party, verify that your relying party publishes the `dca` claim (step 1 above) before you rely on absence as a signal. For the full `dca` value table and other claims, see [XBOX services security token claims](/services/xbox-services/fundamentals/s2s-auth-calls/service-authentication/security-tokens/live-token-claims). For a sample decoded token that shows the `xdi.dca` field, see [Example XSTS Token, decryption, and validation](/services/xbox-services/fundamentals/s2s-auth-calls/service-authentication/security-tokens/live-sample-xsts-token).

<Note>Client-side, the game itself can call [`XGameStreamingIsStreaming`](/build/core-features/common/game-streaming/game-streaming-am-i-streaming) to detect an active streaming connection. The `dca` claim is the equivalent server-side signal for your title service.</Note>

## Device pairwise ID (`dpi`) on XBOX Game Streaming servers

The Device pairwise ID (`dpi`) claim identifies the physical hardware that minted the token. On XBOX Game Streaming servers, that hardware is a shared server in an Azure datacenter, so the same `dpi` value can appear for multiple different users over time.

If your service enforces per-device bans or per-device rate limits using `dpi`, gate that enforcement on the `dca` value first. When `dca` indicates a streaming server, exclude the token's `dpi` from device-level bans and rate limits so you don't penalize unrelated users who later stream from the same server.


## Related topics

- [Optimizing your game for XBOX Game Streaming](/build/core-features/common/game-streaming/game-streaming-optimizing-your-game.md)
- [Server-side handling of XBOX services User Privileges](/services/xbox-services/fundamentals/identity/privileges/concepts/live-user-privileges-server.md)
- [XGameStreaming](/reference/system/xgamestreaming/xgamestreaming_members.md)
- [ClaimServerLobby](/services/playfab/multiplayer/lobby/unity-multiplayer-api-reference/PlayFab.Multiplayer/PlayFabMultiplayer.PlayFabMultiplayerServer/ClaimServerLobby.md)
- [PFMultiplayerClaimServerLobby](/services/playfab/multiplayer/lobby/playfabmultiplayerreference-cpp/pflobby/functions/pfmultiplayerclaimserverlobby.md)