tencent cloud

Tencent Real-Time Communication

お知らせ・リリースノート
製品アップデート情報
Tencent Cloudオーディオビデオ端末SDKの再生アップグレードおよび承認チェック追加に関するお知らせ
TRTCアプリケーションのサブスクリプションパッケージサービスのリリースに関する説明について
製品の説明
製品概要
基礎概念
製品の機能
製品の強み
ユースケース
性能データ
購入ガイド
Billing Overview
無料時間の説明
Monthly subscription
Pay-as-you-go
TRTC Overdue and Suspension Policy
課金に関するよくあるご質問
Refund Instructions
初心者ガイド
Demo体験
Call
コンポーネントの説明(TUICallKit)
Activate the Service
Run Demo
クイック導入
オフライン通知
Conversational Chat
クラウドレコーディング(TUICallKit)
AI Noise Reduction
インターフェースのカスタマイズ
Calls integration to Chat
Additional Features
No UI Integration
Server APIs
Client APIs
Solution
ErrorCode
公開ログ
よくある質問
ライブ配信
Billing of Video Live Component
Overview
Activating the Service (TUILiveKit)
Demo のクイックスタート
No UI Integration
UI Customization
Live Broadcast Monitoring
Video Live Streaming
Voice Chat Room
Advanced Features
Client APIs
Server APIs
Error Codes
Release Notes
FAQs
RTC Engine
Activate Service
SDKのダウンロード
APIコードサンプル
Usage Guidelines
クライアント側 API
高度な機能
RTC RESTFUL API
History
Introduction
API Category
Room Management APIs
Stream mixing and relay APIs
On-cloud recording APIs
Data Monitoring APIs
Pull stream Relay Related interface
Web Record APIs
AI Service APIs
Cloud Slicing APIs
Cloud Moderation APIs
Making API Requests
Call Quality Monitoring APIs
Usage Statistics APIs
Data Types
Appendix
Error Codes
コンソールガイド
アプリケーション管理
使用統計
監視ダッシュボード
開発支援
Solution
Real-Time Chorus
よくあるご質問
課金関連問題
機能関連
UserSig関連
ファイアウォールの制限の対応関連
インストールパッケージの圧縮に関するご質問
AndriodおよびiOS関連
Web端末関連
Flutter関連
Electron関連
TRTCCalling Web関連
オーディオビデオ品質関連
その他のご質問
旧バージョンのドキュメント
TUIRoom(Web)の統合
TUIRoom (Android)の統合
TUIRoom (iOS)の統合
TUIRoom (Flutter)の統合
TUIRoom (Electron)の統合
TUIRoom APIのクエリー
クラウドレコーディングと再生の実現(旧)
Protocols and Policies
セキュリティコンプライアンス認証
セキュリティホワイトペーパー
情報セキュリティの説明
Service Level Agreement
Apple Privacy Policy: PrivacyInfo.xcprivacy
TRTC ポリシー
プライバシーポリシー
データ処理とセキュリティ契約
用語集
ドキュメントTencent Real-Time Communication

Generate UserSig

フォーカスモード
フォントサイズ
最終更新日: 2025-12-22 17:00:24
UserSig is the password for user login and also the signature for using RestAPI. It is essentially the ciphertext obtained by encrypting UserID and other information. This article will guide you on how to generate UserSig.
Note:
Live system and Instant Messaging (Chat) system share the same usersig generation method.

Obtaining a Key

1. Log in to the Chat console.
Note:
If you do not have any app, please Activating the Service to create app.
2. Click the target app card to go to its basic configuration page.
3. In the Basic Information section, click Display key to the right of Key.

4. Click Copy to copy and save the key information.
Note:
Store the key information properly to prevent disclosure.

Calculating UserSig on the Client

The GenerateTestUserSig open-source module provided in the sample code of the Chat SDK can help you quickly generate a UserSig. You only need to configure three member variables, including SDKAPPID (SDKAppID of the app), EXPIRETIME (UserSig expiration time), and SECRETKEY (key information), and then call the genTestUserSig() function to quickly obtain a UserSig.
To simplify this process, we provide the source code for computing a UserSig for the following languages and platforms. You can directly download and integrate the source code into your client.
Programing Language
Platform
GenerateTestUserSig Source Code
Java
Android
Objective-C
iOS
Objective-C
Mac
C++
Windows
Javascript
Web
Dart
Flutter
Note:
In this method, the SECRETKEY is vulnerable to decompilation and reverse engineering. Once your SECRETKEY is disclosed, attackers can steal your Tencent Cloud traffic. Therefore, this method is only suitable for locally running a demo project and feature debugging.
The correct way to issue a UserSig is to integrate the UserSig computing code into your server and provide app-oriented APIs. When UserSig is needed, your app will send a request to the business server to obtain a dynamic UserSig. For more information, see How to Calculate UserSig.

Calculating UserSig on the Server


Generating a UserSig
on the server provides maximum protection against the disclosure of the key used for calculating the UserSig. You only need to deploy the code for calculating the UserSig on your server and provide an app-oriented API. When a UserSig is needed, your app will send a request to the business server to obtain a dynamic UserSig.
To simplify this process, we provide the source code for calculating a UserSig for the following languages and platforms. You can directly download and integrate the source code into your server.
Programming Language
Key Function
Download URL
Java
HMAC-SHA256
genSig
GO
HMAC-SHA256
GenSig
PHP
HMAC-SHA256
genSig
Nodejs
HMAC-SHA256
genSig
Python
HMAC-SHA256
gen_sig
C#
HMAC-SHA256
GenSig
C++
HMAC-SHA256
gen_sig
Key fields in a UserSig calculation function include the SDKAppID, UserID, and UserSig validity period, as described in the following table.
Note:
The following table uses the field names in the Java source code as an example. The field names may be different in other languages.
Field Name (Example)
Description
sdkappid
SDKAppID of the app. You can obtain the SDKAppID on the app card in the Chat console.
userId
User ID (former name: Identifier).
expire
UserSig validity period, in seconds. It is recommended that the UserSig validity period be no less than 24 hours and no more than 50 years. For the security of your account, it is recommended that the UserSig validity period be set to two months.
userbuf
This field is set to null by default because APIs without UserBuf are used in Chat by default.
key
Key. You can obtain a key on the app details page in the Chat console.

Old Version of Algorithm

To simplify signature computing so that customers can conveniently and quickly use Tencent Cloud services, the signature algorithm of the Chat service has been upgraded from ECDSA-SHA256 to HMAC-SHA256 since July 19, 2019. This means that all SDKAppIDs created after July 19, 2019 will use the new HMAC-SHA256 algorithm.
If your SDKAppID was created before July 19, 2019, we recommend that you upgrade the signature algorithm to HMAC-SHA256. The upgrade will not affect your business. Alternatively, you can still use the signature algorithm of an earlier version. The URLs for downloading the source code for the ECDSA-SHA256 algorithm are as follows:
Programming Language
Signature Algorithm
Download Link
Java
ECDSA-SHA256
GitHub
GO
ECDSA-SHA256
GitHub
PHP
ECDSA-SHA256
GitHub
Nodejs
ECDSA-SHA256
GitHub
Python
ECDSA-SHA256
GitHub
C#
ECDSA-SHA256
GitHub
C++
ECDSA-SHA256
GitHub

Get UserSig from the console

Log in to Tencent-RTC Console, navigate to Development Tools > UserSig Tools.
Under the UserSig Generation Tool, select the corresponding SDKAppID and UserID.
Click the Generate button to compute the corresponding UserSig.





ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック