Using Vivox Access Tokens together with UAS

Follow this workflow to use Vivox Access Tokens together with Unity Authentication Services.

Read time 3 minutes

Last updated a day ago

To have full control over which player can access which channels you can have your own back end mint Vivox Access Tokens (VATs).

Tip

This flow is especially useful for projects with an existing VAT flow to leverage the full Vivox Safety suite or other Unity services.

Important

Only use this flow if you need additional channel access control that can't be achieved with regular UAS tokens or if you're an existing VAT user and want to integrate with Unity Authentication Services (UAS).

Prerequisites:

Set up a Unity Cloud project
- Make sure you have your project ID, environment ID, and environment name.
Enable the UAS custom ID provider
- Make sure you have your Service Account credentials handy from this setup.

Creating VATs

The Vivox SDK will request a VAT from the back end whenever one is needed using a custom token provider implementation.
Add the
```
accessToken
```
to the request to the back end when requesting VATs within the
```
GetTokenAsync
```
method.
Validate and extract the needed information from the token in the back end and create the Vivox access token to send it back to the client.

VAT creation flow

This diagram covers the flow of creating VATs while using UAS:

The game client sends UAS access tokens to the game back end
The game back end either gets token validation from the Unity Authentication Service with a JWKS refresh or validates the token itself using UAS player ID and environment ID.
Once validated the game back end then returns a VAT to the game client.

Client-side setup

In your game client, create a class that implements the Vivox SDK’s

IVivoxTokenProvider

interface and register it with the VivoxService. When you register your implementation of IVivoxTokenProvider by calling

VivoxService.Instance.SetTokenProvider

, Vivox calls your implementation's

IVivoxTokenProvider.GetTokenAsync

method whenever a token is needed for actions such as logging in. The information needed to create a payload is provided as input to the overridden

IVivoxTokenProvider.GetTokenAsync

method. This information is used when crafting a VAT. You must still set up server-side token vending and fetch the token within the overridden

IVivoxTokenProvider.GetTokenAsync

method. Before logging in your player, you must register your

IVivoxTokenProvider

implementation using:


VivoxService.Instance.SetTokenProvider(new CustomTokenProvider());

Important

The subscribe flow changed in v16.5.0. For Unity Vivox SDK versions previous to 16.5.0, you must register your

IVivoxTokenProvider

implementation before initializing the Vivox SDK.

Fetch the token

Create the payload with all the parameters provided in the overridden method, even if some are empty, and send it to your secure server to generate your Vivox Access Token. Best practice is to send all the parameters; only what’s needed for the payload will be returned. Use the payload as input in the

GetTokenAsync

method. Additionally, you will have to send the UAS

accessToken

in the payload of the request for the server to validate it and generate the Vivox Access Token from it. For certain tokens, different parameters will be empty. For example,

targetUserUri

and

channelUri

will be empty for a login token. This is expected behavior. The following is an example of token generation:


public class VoiceManager : MonoBehaviour{    async void Start()    {        // Must be done before any other Vivox action otherwise tokens will not be generated properly.        VivoxService.Instance.SetTokenProvider(new VivoxTokenProvider());        await UnityServices.InitializeAsync();        await VivoxService.Instance.InitializeAsync();    }}class VivoxTokenProvider : IVivoxTokenProvider{    public Task<string> GetTokenAsync(string issuer = null, TimeSpan? expiration = null, string targetUserUri = null, string action = null, string channelUri = null, string fromUserUri = null, string realm = null)    {        if (!AuthenticationService.Instance.SessionTokenExists)        {          // Player not logged in!        }        var accessToken = AuthenticationService.Instance.AccessToken        // Implement token fetching logic here.        // The method parameters together with the accessToken from the AuthenticationService contain the necessary information for crafting the request payload.        // This will be called whenever a token is needed for a Vivox action    }}

Server-side setup

Your back end service needs to expose an API that the client can invoke within the

GetTokenAsync

function above, to receive a VAT when it's needed. Refer to Generate a token on a secure server to learn more about the implementation details on how to create a VAT. Refer to Access token payload for more information on the token payload. When creating the VATs you need to be using the following user SIP URI as the subject:


sip:.issuer.unity_player_id.unity_environment_id.@domain.vivox.com

The

issuer

refers to the Vivox issuer of your Unity project. The

unity_player_id

refers to the UAS player ID. The

unity_environment_id

refers to the environment ID from your Unity Cloud environment. The VAT also requires the following format for the channel SIP URI in the token:


sip:confctl-g-issuer.channel_name.unity_environment_id@domain.vivox.com

The

refers to the channel type: supported values

e, g, d

. The

issuer

refers to the Vivox issuer of your Unity project. The

channel_name

can be any identifier used by the game client. The

unity_environment_id

refers to the environment ID from your Unity Cloud environment. The

unity_player_id

and

unity_environment_id

can be extracted from the accessToken that should be sent from the client to the backend within the

GetTokenAsync

method. Validate the

accessToken

by following the steps described in Validate the token ID. The

sub

claim of the token contains the UAS player ID. The

aud

claim of the token contains the environment ID. The

aud

value is an array of case-sensitive strings, each containing a StringOrURI value.


{  "header": {    "alg": "RS256",    "kid": "<id>",    "typ": "JWT"  },  "payload": {    "aud": [      "upid:{{unity_project_id}}",      "envName:{{environment_name}}",      "envId:{{unity_environment_id}}" // unity environment id    ],    "exp": 1617677595, // expires at    "iat": 1617673872, // issued at    "nbf": 1617673872, // not valid before    "sub": "{{unity_player_id}}", // UAS player ID    "project_id": "{{unity_project_id}}" // unity project id  }}

With that you can create the VAT and return it to the client.

Documentation

Development

User Acquisition

Monetization

Industry

Documentation

Development

User Acquisition

Monetization

Industry

Vivox Unity SDK

Vivox Unity SDK

Using Vivox Access Tokens together with UAS

Creating VATs

VAT creation flow

Client-side setup

Fetch the token

Server-side setup

Using Vivox Access Tokens together with UAS

Creating VATs

VAT creation flow

Client-side setup

To subscribe

Fetch the token

Server-side setup