What are the Token authentication methods for Express SDK, and how should they be used?
Introduction
Express SDK's Token authentication is divided into Basic Authentication Token and Permission Authentication Token. Developers can choose the appropriate authentication method based on their business scenarios.
Authentication refers to verifying whether a user has the permission to access the system to avoid security risks caused by missing permission control or improper operations. ZEGO authenticates users through Token (including Basic Authentication Token and Permission Authentication Token).
| Authentication Method | Description | Application Scenario |
|---|---|---|
| Basic Authentication Token | Developers must bring the Token parameter when logging into a room to verify the legitimacy of the user. | Basic Authentication Token is the basic capability of Token, used for simple permission verification scenarios in business. In most cases, generating this Token is sufficient. |
| Permission Authentication Token | To further improve security, two permission bits for room ID and stream publishing ID have been opened, which can verify the room ID and stream publishing ID for room login. | The general use cases for room ID and stream publishing ID permission bits are as follows:
|
Basic Authentication Token has related permissions enabled by default. Permission Authentication Token requires contacting ZEGOCLOUD Technical Support to enable related permissions.
Different platforms' SDK support for using Token authentication functionality varies (refer to the version numbers below). You can query your current SDK version through the getVersion interface to confirm whether this feature is supported.
- iOS/Android/macOS/Windows/Unity3D: Version 2.17.0 and above
- Flutter: Version 2.17.1 and above
- React Native: Version 0.17.0 and above
- uni-app: Version 1.5.0 and above
- Electron: Version 2.17.3 and above
- Linux (C++): Version 2.17.3 and above
Implementation Process
Please select the corresponding documentation below based on your business development platform to implement Token authentication.
| Product | Reference Documentation |
|---|---|
| Video Call | |
| Real-time Voice |
