Considerations for managing authorization in Vivox.
Read time 1 minuteLast updated a day ago
All secured actions require authorization through an access token before they can be successfully carried out. This includes the following actions:
Logging in
Joining a channel
Kicking a user from a channel
Muting a user in a channel
The recommended approach for authorization actions in this category is to authorize the requested action (for example, joining an area or match chat, or joining a party chat) by generating an access token and then delivering it to the client.During development, you can generate insecure access tokens on the client by using the appropriate Client API call (
vx_debug_generate_token
).In production, authorize secured voice actions by using a separate, trusted party, such as a game server. Configure the game server to create access tokens and then pass them to the game client to submit to Vivox APIs that require those tokens.For more information, refer to the Access Token Developer Guide.