Symptom
This article explains the differences in authentication between the OpenTok environment and the Unified environment. For an overview of the complete migration process, please refer to this article.
Applies To
- Video API customers planning to migrate from the OpenTok environment to the Unified environment
- Authentication
Resolution
In the OpenTok environment, each project uses a Project API Key and Project Secret.
In the Unified environment, projects are replaced by Applications, and authentication is performed using an Application ID and the corresponding Private Key generated for each application.
| OpenTok | Unified |
|
Project key (Example: 12345678)
|
Application ID (Example: abc123-abc123-abc123-abc123)
|
| Project secret (Example: abc123...) |
Private key (Example: -----BEGIN PRIVATE KEY----- |
| Account key (Example: 12345678) | Account key (Example: abc123...) |
| Account secret (Example: abc123...) | Account secret (Example: abc123...) |
Additional Information
Articles in this section
- Migrating Video REST API from OpenTok to Unified
- Video Client SDK Changes from OpenTok to Unified
- How to Migrate from OpenTok Server SDK to Unified Server SDK
- Credential Differences Between OpenTok and Unified Environments
- In which Regional Media Zones can I use Experience Composer?
- How do I monitor Video API call quality in real-time?
- JWT Tokens in the TokBox and Unified Environments
- Android SDK 2.28.2 error when using the application context
- What happens if your session lasts more than 8 hours?
- Updates to using the Vonage Media Library in Native SDKs from version 2.27.x onwards