Deploy the VFC Recording Controls Application

Prepare the VFC Recording Controls Application Bundle

This bundle vmr-shell<build-number>.zip file, contains manifest.json file and two icon files.   Edit the manifest.json file of this bundle as following:

Step 1 - Replace {{teams-app-id}} with the App ID of the Teams app created above.

Step 2-  Replace all instances of {{verba-base-url}} with the Verba server’s base URL

Example:

{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.14/MicrosoftTeams.schema.json",
  "version": "1.0.0",
  "manifestVersion": "1.14",
  "id": "150a0b12-9475-4b4f-8928-aef33d7d401e",
  "packageName": "com.package.name",
  "name": {
...
"staticTabs": [
        {
            "entityId": "index",
            "name": "Recording Tab",
            "contentUrl": https://verbapool1app.demolab.com/verba/msTeamsApp,
            "websiteUrl": https://verbapool1app.demolab.com/verba/msTeamsApp,
            "scopes": [
                "personal"
            ]
        }
    ],

Step 3 - Replace {{verba-server-domain}} with the Verba server’s domain name

Example:

"validDomains": [
"verbapool1app.verintenglab.com"
]

Step 4 - Replace all instances of {{azure-app-id}} with "Application (client) ID" of the Azure AD Application created above.

Example:

"webApplicationInfo": {

         "id": "3ebcfff6-0b0b-4d8b-91d4-9b2a292c529e",
         "resource": "api://verbapool1app.verintenglab.com/3ebcfff6-0b0b-4d8b-91d4-9b2a292c529e"
}

Upload the VFC Recording Controls Application Bundle

Step 1 - Login to MS Teams Admin Portal https://admin.teams.microsoft.com/

Step 2 - Go to Teams / Manage app and choose “Upload new app”, and upload the app bundle prepared above.

Deploy the VFC Recording Controls Application Bundle onto Verba Server

Step 1 - Copy and explode the app bundle vrm-spa<build-number>.zip file into [VERBA-APP-INSTALL-FOLDER]\tomcat\webapps\verba\msTeamsApp\spa folder (example C:\Program Files\Verba\tomcat\webapps\verba\msTeamsApp\spa).

The app files look like this after deployed:

Configure the Verba Server for the VFC Recording Controls Application 

Step 1 - The app only works over HTTPS protocol (with a public CA certificate), so make sure that is enabled in the Tomcat configuration. Instructions for this can be found here: Installing an SSL certificate for HTTPS access

Step 2 - The app application must use the following cookie settings: SameSite: none.

To achieve that open this file

[VERBA-APP-INSTALL-FOLDER]\Verba\tomcat\webapps\verba\META-INF\context.xml

Change the "CookieProcessor" tag "sameSiteCookies"  attribute value from "lax" to "none".

<CookieProcessor sameSiteCookies="none" />

Step 3 -  The frame-ancestors Content Settings Policy header must allow the embedding from Microsofts' domain. That is a default configuration of the web application since 9.7.5. If this header is missing, it can be turned on via this registry key (create it if it doesn't exist yet, type: REG_SZ):

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Verba\Web\HeaderSecurityCSP

The following value should be appended to the current CSP header and stored in the registry:

frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com;

Example:

default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; frame-src 'self' mailto: tel:; frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com;

Step 4 - Restart the web application service.

Link Users on the Verba Server

Step 1 - Import users into with "Azure AD sync" Active Directory synchronization

Step 2 - Setup an "Identity Provider" with the same Azure AD application as it was created above Identity providers

Step 3 - Associate the newly created "Identity Provider" with Verba users. The quickest way is to associate the "Identity Provider" with “Standard User” role in Verba