tencent cloud

Tencent Real-Time Communication

Release Notes and Announcements
Release Notes
Recent Product Announcement
TRTC Live (TUILiveKit) Product Launch Announcement
TRTC Conference Official Editions Launched
The commercial version of Conference is coming soon
Terms and Conditions Applicable to $9.9 Starter Package
Rules for the "First Subscription $100 Discount" Promotion
Announcement on the Start of Beta Testing for Multi-person Audio and Video Conference
TRTC Call Official Editions Launched
License Required for Video Playback in New Version of LiteAV SDK
TRTC to Offer Monthly Packages
Product Introduction
Overview
Concepts
Features
Strengths
Use Cases
Performance Statistics
Tencent RTC Quickplay: Experience Ultimate Real-Time Audio and Video Interaction!
Purchase Guide
Billing Overview
Free Minutes
Monthly subscription
Pay-as-you-go
TRTC Overdue and Suspension Policy
FAQs
Refund Instructions
User Tutorial
Free Demo
Call
Overview
Activate the Service
Run Demo
Integration
Offline Call Push
Conversational Chat
On-Cloud Recording
AI Noise Reduction
UI Customization
Calls integration to Chat
Additional Features
No UI Integration
Server APIs
Client APIs
Solution
ErrorCode
Release Notes
FAQs
Conference
Overview(TUIRoomKit)
Activate the Service (TUIRoomKit)
Run Demo(TUIRoomKit)
Integration(TUIRoomKit)
Screen Sharing (TUIRoomKit)
Schedule a meeting (TUIRoomKit)
In-meeting Call (TUIRoomKit)
UI Customization(TUIRoomKit)
Virtual Background (TUIRoomKit)
Conference Control (TUIRoomKit)
Cloud Recording (TUIRoomKit)
AI Noise Reduction (TUIRoomKit)
In-Conference Chat (TUIRoomKit)
Robot Streaming (TUIRoomKit)
Enhanced Features (TUIRoomKit)
Client APIs (TUIRoomKit)
Server APIs (TUIRoomKit)
FAQs (TUIRoomKit)
Error Code (TUIRoomKit)
SDK Update Log (TUIRoomKit)
Live
Billing of Video Live Component
Overview
Activating the Service (TUILiveKit)
Run 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 Download
API Examples
Usage Guidelines
API Reference Manual
Advanced Features
AI Integration
Overview
Configure MCP Server
Install Skills
Integration Guide
FAQ
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
Console Guide
Application Management
Package Management
Usage Statistics
Monitoring Dashboard
Development Assistance
Solution
Real-Time Chorus
FAQs
Migration Guide
Billing
Features
UserSig
Firewall Restrictions
How to Downsize Installation Package
Android and iOS
Web
Flutter
Electron
TRTCCalling for Web
Audio and Video Quality
Others
Legacy Documentation
RTC RoomEngine SDK(Old)
Integrating TUIRoom (Web)
Integrating TUIRoom (Android)
Integrating TUIRoom (iOS)
Integrating TUIRoom (Flutter)
Integrating TUIRoom (Electron)
TUIRoom APIs
On-Cloud Recording and Playback (Old)
RTC Analytics Monthly Packages (Previous Version)
Protocols and Policies
Compliance
Security White Paper
Notes on Information Security
Service Level Agreement
Apple Privacy Policy: PrivacyInfo.xcprivacy
TRTC Policy
Privacy Policy
Data Processing And Security Agreement
Glossary

Login Authentication

PDF
Focus Mode
Font Size
Last updated: 2025-05-20 10:41:46

Login Authentication Overview

Live and Instant Messaging (Chat) share the same login authentication system, Instant Messaging (Chat) evolved from the QQ instant messaging system. We extracted QQ’s common modules and integrated them to build the integration-friendly Chat SDK and backend service.
The Chat SDK can be viewed as QQ without the user interface. Integrating the Chat SDK into your app is similar to integrating the QQ kernel.
You must log in to QQ before you can use it for messaging. While you log in to QQ with your QQ ID and password, you must log in to the Chat SDK with the specified username (UserID) and password (UserSig).
UserID: Formerly known as Identifier. This is the username for users to log in to Chat. It is actually the user ID in your app.
For example, if a user in your app has the ID of 27149, you can use 27149 as the UserID to log in to Chat.
UserSig: This is the password with which the user logs in to Chat. It is the data generated after App Server uses the key to encrypt info such as UserID. For more information, see Generating UserSig.

App Login Process

We recommend that apps log in to Chat as follows:



Caution
The Chat backend completely trusts UserSig. To avoid affecting your data and business, you must ensure the security of the private key.
UserSigs generated by the default API of the Chat backend SDK are valid for 180 days. Developers can use the API with the validity parameter to customize the validity period. Developers must obtain a new UserSig from the developer backend before the original UserSig expires.
For more information on the Chat backend SDK that is used to generate UserSig, see Generating UserSig.

App Admin

Some Chat services require admin permissions, for example, calling RESTful APIs, disbanding a group, and pushing to all group members. Compared with ordinary accounts, the role of app admin has the highest level of privileges:
It has higher read permissions. For example, it can obtain all groups within the app and any information about any group.
It has higher operation permissions. For example, it can send messages to any user and add or delete members in any group.
You can only set app admins in the console. For more information on the procedure, see Configuring Account Admins.



Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback