Authenticate Your Users with Tokens

Authentication is the act of validating the identity of each user before they access your system. Agora uses digital tokens to authenticate users and their privileges before they access an Agora service, such as joining an Agora call, or logging into the real-time messaging system.

To enhance its authentication and security services, Agora provides a new version of token called AccessToken2 as of August 18, 2022. For how to upgrade from AccessToken to AccessToken2, see Upgrade from AccessToken to AccessToken2.

This page shows you how to create a token server and a client app for AccessToken2. The client app retrieves a token from the token server. This token authenticates the current user when the user accesses the Agora service.

Understand the tech

The following figure shows the steps in the authentication flow:

token authentication flow

A token is a dynamic key generated on your app server that is valid for a maximum of 24 hours. When your users connect to an Agora channel from your app client, Agora Platform validates the token and reads the user and project information stored in the token. A token contains the following information:

The App ID of your Agora project
The channel name
The user ID of the user to be authenticated
The privilege of the user, either as a publisher or a subscriber
The time after which the token expires

Prerequisites

In order to follow this procedure you must have the following:

A valid Agora account.
An Agora project with the App Certificate enabled.
Golang 1.14+ with GO111MODULE set to on.
If you are using Go 1.16+, GO111MODULE is on by default. See this blog for details.
npm and a supported browser.

Implement the authentication flow

This section shows you how to supply and consume a token that gives rights to specific functionality to authenticated users using the source code provided by Agora.

Get the App ID and App Certificate

This section shows you how to get the security information needed to generate a token, including the App ID and App Certificate of your project.

1. Get the App ID

Agora automatically assigns each project an App ID as a unique identifier.

To copy this App ID, find your project on the Project Management page in Agora Console, and click the copy icon in the App ID column.

2. Get the App Certificate

To get an App Certificate, do the following:

On the Project Management page, click Config for the project you want to use.
Click the copy icon under Primary Certificate.

Deploy a token server

Token generators create the tokens requested by your client app to enable secure access to Agora security infrastructure. To serve these tokens you deploy a generator in your security infrastructure.

In order to show the authentication workflow, this section shows how to build and run a token server written in Golang on your local machine.

This sample server uses BuildTokenWithUid[1/2].

This sample server is for demonstration purposes only. Do not use it in a production environment.

Create a file, server.go, with the following content. Then replace <Your App ID> and <Your App Certificate> with your App ID and App Certificate.

package main
import (
    rtctokenbuilder "github.com/AgoraIO/Tools/DynamicKey/AgoraDynamicKey/go/src/rtctokenbuilder2"
    "fmt"
    "log"
    "net/http"
    "encoding/json"
    "errors"
    "strconv"
)
type rtc_int_token_struct struct{
    Uid_rtc_int uint32 `json:"uid"`
    Channel_name string `json:"ChannelName"`
    Role uint32 `json:"role"`
}
var rtc_token string
var int_uid uint32
var channel_name string
var role_num uint32
var role rtctokenbuilder.Role
// Use RtcTokenBuilder to generate an RTC token.
func generateRtcToken(int_uid uint32, channelName string, role rtctokenbuilder.Role){
    appID := "<Your App ID>"
    appCertificate := "<Your App Certificate>"
    // Number of seconds after which the AccessToken2 expires.
    // When the AccessToken2 expires but the privilege does not expire, the user remains in the channel and can continue to publish streams. No callback is triggered from the SDK.
    // However, once disconnected from the channel, the user cannot rejoin the channel with that token. Ensure the AccessToken2 does not expire before the privileges.
    tokenExpireTimeInSeconds := uint32(40)
    // Number of seconds after which the privilege expires.
    // The token-privilege-will-expire callback occurs 30 seconds before the privilege expires.
    // The token-privilege-did-expire callback occurs when the privilege expires.
    // For demonstration purposes the expire time is set to 40 seconds. This shows you the automatic token renew actions of the client.
    privilegeExpireTimeInSeconds := uint32(40)
    result, err := rtctokenbuilder.BuildTokenWithUid(appID, appCertificate, channelName, int_uid, role, tokenExpireTimeInSeconds, privilegeExpireTimeInSeconds)
    if err != nil {
        fmt.Println(err)
    } else {
        fmt.Printf("Token with uid: %s\n", result)
        fmt.Printf("uid is %d\n", int_uid )
        fmt.Printf("ChannelName is %s\n", channelName)
        fmt.Printf("Role is %d\n", role)
    }
    rtc_token = result
}
func rtcTokenHandler(w http.ResponseWriter, r *http.Request){
    w.Header().Set("Content-Type", "application/json; charset=UTF-8")
    w.Header().Set("Access-Control-Allow-Origin", "*")
    w.Header().Set("Access-Control-Allow-Methods", "POST, OPTIONS");
    w.Header().Set("Access-Control-Allow-Headers", "*");
    if r.Method == "OPTIONS" {
        w.WriteHeader(http.StatusOK)
        return
    }
    if r.Method != "POST" && r.Method != "OPTIONS" {
        http.Error(w, "Unsupported method. Please check.", http.StatusNotFound)
        return
    }
    var t_int rtc_int_token_struct
    var unmarshalErr *json.UnmarshalTypeError
    int_decoder := json.NewDecoder(r.Body)
    int_err := int_decoder.Decode(&t_int)
    if (int_err == nil) {
                int_uid = t_int.Uid_rtc_int
                channel_name = t_int.Channel_name
                role_num = t_int.Role
                switch role_num {
                    case 1:
                        role = rtctokenbuilder.RolePublisher
                    case 2:
                        role = rtctokenbuilder.RoleSubscriber
                }
    }
    if (int_err != nil) {
        if errors.As(int_err, &unmarshalErr){
                errorResponse(w, "Bad request. Wrong type provided for field " + unmarshalErr.Value  + unmarshalErr.Field + unmarshalErr.Struct, http.StatusBadRequest)
                } else {
                errorResponse(w, "Bad request.", http.StatusBadRequest)
            }
        return
    }
    generateRtcToken(int_uid, channel_name, role)
    errorResponse(w, rtc_token, http.StatusOK)
    log.Println(w, r)
}
func errorResponse(w http.ResponseWriter, message string, httpStatusCode int){
    w.Header().Set("Content-Type", "application/json")
    w.Header().Set("Access-Control-Allow-Origin", "*")
    w.WriteHeader(httpStatusCode)
    resp := make(map[string]string)
    resp["token"] = message
    resp["code"] = strconv.Itoa(httpStatusCode)
    jsonResp, _ := json.Marshal(resp)
    w.Write(jsonResp)
}
func main(){
    // RTC token from RTC int uid
    http.HandleFunc("/fetch_rtc_token", rtcTokenHandler)
    fmt.Printf("Starting server at port 8082\n")
    if err := http.ListenAndServe(":8082", nil); err != nil {
        log.Fatal(err)
    }
}

A go.mod file defines this module’s import path and dependency requirements. To create the go.mod for your token server, run the following command:

_1$ go mod init sampleServer
Get dependencies by running the following command. You can use a Go mirror origin such as https://goproxy.cn/ to speed up the process.

_1$ go get
Start the server by running the following command:

_1$ go run server.go

Use AccessToken2 for client-side user authentication

This section uses the Web client as an example to show how to use a token for client-side user authentication.

This sample client is for demonstration purposes only. Do not use it in a production environment.

Create the project structure of the Web client with a folder including the following files.
- index.html: User interface
- client.js: App logic with Agora RTC Web SDK v4.x (Must be v4.8.0 or higher)
_3| _3|-- index.html _3|-- client.js
In index.html, add the following code to include the app logic in the UI:

_13<html> _13<head> _13 <title>Token demo</title> _13</head> _13<script src="https://unpkg.com/axios/dist/axios.min.js"></script> _13<body> _13 <h1>Token demo</h1> _13 _13 <script src="https://download.agora.io/sdk/release/AgoraRTC_N-4.8.0.js""></script> _13 <script src="./client.js"></script> _13 _13</body> _13</html>
Create the app logic by editing client.js with the following content:

Replace <Your App ID> with your App ID. The App ID must match the one in the server.
Replace <Your Host URL and port> with the host URL and port of the local Golang server you have just deployed, such as 10.53.3.234:8082.

var rtc = {
     // For the local audio and video tracks.
     localAudioTrack: null,
     localVideoTrack: null,
 };
 var options = {
     // Passes your app ID here.
     appId: "<Your app ID>",
     // Sets the channel name.
     channel: "ChannelA",
     // Sets the user role in the channel.
     role: "host"
 };
 // Fetches a token from the Golang server.
 function fetchToken(uid, channelName, tokenRole) {
     return new Promise(function (resolve) {
         axios.post('http://<Your Host URL and port>/fetch_rtc_token', {
             uid: uid,
             channelName: channelName,
             role: tokenRole
         }, {
             headers: {
                 'Content-Type': 'application/json; charset=UTF-8'
             }
         })
             .then(function (response) {
                 const token = response.data.token;
                 resolve(token);
             })
             .catch(function (error) {
                 console.log(error);
             });
     })
 }
 async function startBasicCall() {
     const client = AgoraRTC.createClient({ mode: "live", codec: "vp8" });
     client.setClientRole(options.role);
     const uid = 123456;
     // Fetches a token before calling join to join a channel.
     let token = await fetchToken(uid, options.channel, 1);
     await client.join(options.appId, options.channel, token, uid);
     rtc.localAudioTrack = await AgoraRTC.createMicrophoneAudioTrack();
     rtc.localVideoTrack = await AgoraRTC.createCameraVideoTrack();
     await client.publish([rtc.localAudioTrack, rtc.localVideoTrack]);
     const localPlayerContainer = document.createElement("div");
     localPlayerContainer.id = uid;
     localPlayerContainer.style.width = "640px";
     localPlayerContainer.style.height = "480px";
     document.body.append(localPlayerContainer);
     rtc.localVideoTrack.play(localPlayerContainer);
     console.log("publish success!");
     client.on("user-published", async (user, mediaType) => {
         await client.subscribe(user, mediaType);
         console.log("subscribe success");
         if (mediaType === "video") {
             const remoteVideoTrack = user.videoTrack;
             const remotePlayerContainer = document.createElement("div");
             remotePlayerContainer.textContent = "Remote user " + user.uid.toString();
             remotePlayerContainer.style.width = "640px";
             remotePlayerContainer.style.height = "480px";
             document.body.append(remotePlayerContainer);
             remoteVideoTrack.play(remotePlayerContainer);
         }
         if (mediaType === "audio") {
             const remoteAudioTrack = user.audioTrack;
             remoteAudioTrack.play();
         }
         client.on("user-unpublished", user => {
             const remotePlayerContainer = document.getElementById(user.uid);
             remotePlayerContainer.remove();
         });
     });
     // When token-privilege-will-expire occurs, fetches a new token from the server and call renewToken to renew the token.
     client.on("token-privilege-will-expire", async function () {
         let token = await fetchToken(uid, options.channel, 1);
         await client.renewToken(token);
     });
     // When token-privilege-did-expire occurs, fetches a new token from the server and call join to rejoin the channel.
     client.on("token-privilege-did-expire", async function () {
         console.log("Fetching the new Token")
         let token = await fetchToken(uid, options.channel, 1);
         console.log("Rejoining the channel with new Token")
         await rtc.client.join(options.appId, options.channel, token, uid);
     });
 }
 startBasicCall()

In the code example, you can see that token is related to the following code logic in the client:

Call join to join the channel with token, user ID, and channel name. The user ID and channel name must be the same as the ones used to generate the token.
The token-privilege-will-expire callback occurs 30 seconds before the privilege expires. When the token-privilege-will-expire callback is triggered, the client must fetch the token from the server and call renewToken to pass the new token to the SDK.
The token-privilege-did-expire callback occurs when the privilege expires. When the token-privilege-did-expire callback is triggered, the client must fetch the token from the server and call join to use the new token to join the channel.

Open index.html with a supported browser to perform the following actions:
- Successfully joining a channel.
- Renewing a token every 10 seconds.

Reference

This section introduces token generator libraries, version requirements, and related documents about AccessToken2.

SDK compatibility for AccessToken2

AccessToken2 supports the following versions of the Agora RTC SDK (excluding the client-side Media Push feature):

SDK	SDK Version to Support AccessToken2
RTC Native SDK	>= 3.6.0
RTC Electron SDK	>= 3.6.0
RTC Unity SDK	>= 3.6.0
RTC React Native SDK	>= 3.6.0
RTC Flutter SDK	>= 5.10
RTC Web SDK	>= 4.8.0

RTC SDKs that use AccessToken2 can interoperate with RTC SDKs that use AccessToken. RTC SDKs that support AccessToken2 also support AccessToken.

AccessToken2 generator libraries

Agora provides an open-source AgoraDynamicKey repository on GitHub, which enables you to generate tokens on your server with programming languages such as C++, Java, and Go.

Language	Algorithm	Core method	Sample code
C++	HMAC-SHA256	buildTokenWithUid	RtcTokenBuilderSample.cpp
Go	HMAC-SHA256	buildTokenWithUid	sample.go
Java	HMAC-SHA256	buildTokenWithUid	RtcTokenBuilderSample.java
Node.js	HMAC-SHA256	buildTokenWithUid	RtcTokenBuilderSample.js
PHP	HMAC-SHA256	buildTokenWithUid	RtcTokenBuilderSample.php
Python	HMAC-SHA256	buildTokenWithUid	RtcTokenBuilderSample.py
Python3	HMAC-SHA256	buildTokenWithUid	RtcTokenBuilderSample.py

BuildTokenWithUid API Reference

This section introduces the core method for generating AccessToken2: BuildTokenWithUid. The AccessToken2 generator libraries provide two BuildTokenWithUid methods:

BuildTokenWithUid [1/2]: Generates an AccessToken2, and sets the expiration for AccessToken2 and the expiration for all privileges.
BuildTokenWithUid [2/2]: Generates an AccessToken2, and sets the expiration for the following:

AccessToken2
The privilege of publishing audio streams in a channel
The privilege of publishing video streams in a channel
The privilege of publishing data streams in a channel

BuildTokenWithUid [1/2]

This method uses a token_expire parameter to set the expiration for AccessToken2 and a privilege_expire parameter to set the expiration for all privileges.

// Take C++ as an example
static std::string BuildTokenWithUid(const std::string& app_id,
                                       const std::string& app_certificate,
                                       const std::string& channel_name,
                                       uint32_t uid, UserRole role,
                                       uint32_t token_expire,
                                       uint32_t privilege_expire = 0);

Parameter	Description
`appId`	The App ID of your Agora project.
`appCertificate`	The App Certificate of your Agora project.
`channelName`	The channel name. The string length must be less than 64 bytes. The following character sets are supported: All lowercase English letters: a to z. All upper English letters: A to Z. All numeric characters: 0 to 9. The space character. Punctuation characters and other symbols, including: "!", "#", "$", "%", "&", "(", ")", "+", "-", ":", ";", "<", "=", ".", ">", "?", "@", "[", "]", "^", "_", " , ", "\|", "~", ",".
`uid`	The user ID of the user to be authenticated. A 32-bit unsigned integer with a value range from 1 to (2³² - 1). It must be unique. Set `uid` as 0, if you do not want to authenticate the user ID, that is, any `uid` from the app client can join the channel.
`role`	The privilege of the user, either as a publisher or a subscriber. This parameter determines whether a user can publish streams in the channel. `kRole_Publisher(1)`: (Default) The user has the privilege of a publisher, that is, the user can publish streams in the channel. `kRole_Subscriber(2)`: The user has the privilege of a subscriber, that is, the user can only subscribe to streams, not publish them, in the channel. This value takes effect only if you have enabled co-host authentication. For details, see Enable co-host authentication.
`token_expire`	The duration (in seconds) from the generation of an AccessToken2 to the expiration of that AccessToken2. For example, if you set it as 600, the AccessToken2 expires 10 minutes after generation. The maximum duration of an AccessToken2 is 24 hours. If you set it to a duration longer than 24 hours, the AccessToken2 still expires after 24 hours. If you set it to 0, the AccessToken2 expires immediately.
`privilege_expire`	The duration (in seconds) from the generation of an AccessToken2 to the expiration of all privileges. For example, if you set it to 600, the privilege expires 10 minutes after generation. If you set it to 0 (default), the privilege never expires.

When the AccessToken2 expires but the privilege does not expire, the user remains in the channel and can continue to publish streams. No token-related callback is triggered in the SDK. However, once disconnected from the channel, the user cannot rejoin the channel with that token. Ensure the AccessToken2 does not expire before privileges.

BuildTokenWithUid [2/2]

To facilitate privilege-level configuration in a channel, Agora provides an overloaded method, BuildTokenWithUid [2/2], to support configuring the expiration of the AccessToken2 and related privileges:

Join a channel
Publish audio streamsin a channel
Publish video streams in a channel
Publish data streams in a channel

// Take C++ as an example
static std::string BuildTokenWithUid(
       const std::string& app_id,
       const std::string& app_certificate,
       const std::string& channel_name,
       uint32_t uid,
       uint32_t token_expire,
       uint32_t join_channel_privilege_expire = 0,
       uint32_t pub_audio_privilege_expire = 0,
       uint32_t pub_video_privilege_expire = 0,
       uint32_t pub_data_stream_privilege_expire = 0);

This method generates an RTC AccessToken2 and supports configuring the expiration time of the token and the following privileges:

Joining an RTC channel
Publishing audio streams in an RTC channel
Publishing video streams in an RTC channel
Publishing data streams in an RTC channel

The privileges of publishing audio streams in an RTC channel, publishing video streams in an RTC channel, and publishing data streams in an RTC channel only take effect after enabling co-host authentication.

You can assign multiple privileges to a user. When a privilege is about to expire or has expired, the RTC SDK triggers the onTokenPriviegeWillExpire callback or the onRequestToken callback. You need to take the following actions in your own app logic:

Tag the type of privilege that is about to expire or has expired in your app logic.
The app fetches a new AccessToken2 from the token server.
The SDK calls renewToken to renew the AccessToken2.

You need to set an appropriate expiration timestamp. For example, if the expiration time of joining a channel is earlier than that of publishing audio in the channel, when the privilege of joining a channel expires, the user is kicked out of the RTC channel. Even if the privilege of publishing audio is still valid, user cannot exercise that privilege.

When the AccessToken2 expires but the privilege of joining a channel does not expire, the user remains in the channel and can continue to publish streams if the corresponding privilege does not expire. No token-related callback is triggered in the SDK. However, once disconnected from the channel, the user cannot rejoin the channel with that token. Ensure the AccessToken2 does not expire before other privileges.

Parameter	Description
`token_expire`	The duration (in seconds) from the generation of an AccessToken2 to the expiration of that AccessToken2. For example, if you set it as 600, the AccessToken2 expires 10 minutes after generation. The maximum duration of an AccessToken2 is 24 hours. If you set it to a duration longer than 24 hours, the AccessToken2 still expires after 24 hours. If you set it to 0, the AccessToken2 expires immediately.
`join_channel_privilege_expire`	The duration (in seconds) from the generation of an AccessToken2 to the expiration of the privilege of joining a channel. For example, if you set it to 600, the privilege expires 10 minutes after generation. If you set it to 0 (default), the privilege never expires.
`pub_audio_privilege_expire`	The duration (in seconds) from the generation of an AccessToken2 to the expiration of the privilege of publishing audio streams in a channel. For example, if you set it to 600, the privilege expires 10 minutes after generation. If you set it to 0 (default), the privilege never expires.
`pub_video_privilege_expire`	The duration (in seconds) from the generation of an AccessToken2 to the expiration of the privilege of publishing video streams in a channel. For example, if you set it to 600, the privilege expires 10 minutes after generation. If you set it to 0 (default), the privilege never expires.
`pub_data_stream_privilege_expire`	The duration (in seconds) from the generation of an AccessToken2 to the expiration of the privilege of publishing data streams in a channel. For example, if you set it to 600, the privilege expires 10 minutes after generation. If you set it to 0 (default), the privilege never expires.

Enable co-host authentication

Refer to the following steps to enable this function in Agora Console:

Log in to Agora Console. Under Projects, choose a project for which you want to enable co-host authentication, click the Config icon, and enter the Edit Project page.
In the Features area, click Enable authentication.
Follow the on-screen instructions to learn more about this function, check the box, and click Enable.

Co-host authentication takes effect in 5 minutes.

Once you have enabled co-host authentication, a user using your app must meet both of the following requirements to publish streams in a channel:

The user role in setClientRole is set as host.
The user joins the channel with a token that has the privilege of a publisher (by setting the role parameter in the buildToken method as kRolePublisher).

Upgrade from AccessToken to AccessToken2

For how to use AccessToken to authenticate your users and how to upgrade to AccessToken2, see Upgrade from AccessToken to AccessToken2.