Kotlin

Setting up authentication

In order to connect to an Vonage Video session, the client will need access to some authentication credentials — an APP ID, session ID, and token. In a production application, these credentials should be generated using a Server SDKs, but to speed things up we will hard code the values for now:

  1. Create a new Kotlin file named VonageVideoConfig.kt and add the following object:
object VonageVideoConfig {
    // Replace with your Vonage Video APP ID
    const val APP_ID = ""
    // Replace with your generated session ID
    const val SESSION_ID = ""
    // Replace with your generated token
    const val TOKEN = ""
}
  1. Adjust the code by hard coding the values for the APP_ID, SESSION_ID and TOKEN. You can obtain them by following the instructions below:

Note: In production applications, they are retrieved from the server more info. For this demo, you can either deploy a Video Learning Server (Node or PHP) and set serverURL or follow the next steps to generate and hardcode them. To get the credentials needed to run the demo:

  • Sign up for or Log into your account.
  • In the left-side menu of the dashboard, click Applications and select a previous application or create a new one to view the Application ID. Screenshot of dashboard with Applications highlighted
Screenshot of dashboard with Application ID highlighted
  • Make sure that Video is activated
Screenshot of dashboard with Video section highlighted
  • Head over to the The Video API Playground. Either enter the Application ID or find it in the dropdown. You can leave the default values for the other options. Click "Create".
Screenshot of The Video API Playground tool
  • Your Session ID and Token will be created.
Screenshot of The Video API Playground tool generated details with the Application ID, Session ID, and Token highlighted in red boxes

Important: You can continue to get the session ID and token values from your Account during testing and development, but before you go into production you must set up a server.

For more information on sessions, tokens, and servers, check out Video API Technical Details.