文档

​
​

Development

User Acquisition

Monetization

工业

Vivox Core SDK

Vivox Core SDK

此页面不支持所选语言。
Vivox
​
​
Vivox Core SDK
  • Overview
  • Before you begin
  • Get started
  • Release notes
  • Developer Guide
  • Reference
    • Access Token Developer Guide
      • Access token terminology
      • Requests that require access tokens
      • Access token identifiers
      • Access token format
      • Access token examples
      • Generate a token on the client
      • Generate a token on a secure server
      • Key update API
      • Override development key generation
      • Access token error codes
    • Server to Server Web API Reference Guide
    • Core API Reference Manual
    • Third-party license information
  • Privacy overview
  1. Vivox Core SDK documentation

Access Token Developer Guide

Learn to generate and manage Vivox Access Tokens for controlling player access.
阅读时间2 分钟
最后更新于 8 个月前

警告
Vivox Access Tokens are an optional, and advanced, feature for managing player channel access. Unity Authentication tokens are the recommended way to manage players when channel access control is not required.
Player access to Vivox resources is controlled through Vivox access tokens (VATs). Vivox access tokens contain a payload that defines the privileged operation, are signed by the game server by using a token signing key, and are delivered by the client to the Vivox system when the player wants to perform a privileged operation. A Vivox access token is similar to a JSON Web Token, but instead has an empty access token header.
Access tokens have the following characteristics:
  • You can only use a token once. After you use a token for the privileged operation, it cannot be reused.
  • Tokens expire even if they are never used. You cannot use a token after the expiration time that is set by the token issuer.
Game clients require access tokens to perform operations in the Vivox system.
  • Game client-generated tokens: Use for prototyping or testing purposes.
  • Secure game server-generated tokens: Use for the secure deployment of a production game and to avoid token errors due to user time settings.
When using Unity Authentication (UAS), Vivox access tokens can parse UASIDs from the token payload. It's mandatory to include embedded UAS IDs in your access tokens if you're using Vivox access tokens with Safe Text.
Refer to the sections titled Generate a token from the client and Generate a token on a secure sever to generate tokens.
Note that before either a client or a server can generate a token, you need a token issuer and a token signing key.
The following diagram displays a typical interaction between a game client, the game server, and the Vivox system:
A diagram showing the token flow.
  1. The game client sends the login request to the game server.
  2. The game server sends back an access token.
  3. The game client sends the access token to Vivox System, which validates the token.
  4. The Vivox system sends back a successful login to the game client.

Copyright © 2026 Unity Technologies
法律信息隐私政策CookiesDocumentation Terms of Use请勿出售或分享我的个人信息您的隐私选择(Cookie 设置)

“Unity”、Unity 徽标及其他 Unity 商标是 Unity Technologies 或其附属公司在美国和其他地方的商标或注册商标(此处查看更多信息)。其他名称或品牌是其各自所有者的商标。

为方便起见,一些页面是机器翻译的,可能包含不准确的内容。如有信息不一致的情况,以英文版本为准。


    报告此页面的问题