Page Comparison

VFC WebEx Meetings Ingestion. 

(Note the application will not be shared on the app hub at present.)

One or more URIs that a user will be redirected to when completing an OAuth grant flow.

http(s)://<VFC Hostname>:<VFC Port>/Webex/RedirectURI/OAuth

VFC Hostname is the name of the VFC server

VFC Port is the port opened in the customer firewall for Webex access.

Make a note of this value as it is also required when configuring the VFC Webex import source.

The port number cannot be 443 as this is already used by the VFC Web Application.

Scopes define the level of access that your integration requires.

Select the following 3 scopes:

• • meeting:recordings_read
  • meeting:recordings_write
  • meeting:participants_read

Mandatory.  Client Id value obtained during previous step of Webex creation integration. Used during OAuth authentication.

Example:

M2lzY29zcGFyazovL3VzL0FQUExJQ0FUSU9OL0MzNWI4NmM0

ATg2Nzc3NmQxNzhiMjg1OGIwMTMzNTdiODJiMTFkZjVlNmM1N

GhiZTlkOGNjNzYyMDcyMTU3M2Mz

Mandatory.  Client Secret value obtained during previous step of Webex creation integration. Used during OAuth authentication.

Example:

0c2e71a7f2628596ad856a9e6ab7efddead07d6b272dc2a2ef3f9fc4cf74d0b7

Mandatory.  URI called by Webex during authentication process. Same value used during configuration of the Webex integration.

http(s)://<VFC Hostname>:<VFC Port>/Webex/RedirectURI/OAuth

VFC Hostname is the name of the VFC server

VFC Port is the port opened in the customer firewall for Webex access.

The port number cannot be 443 as this is already used by the VFC Web Application.

Must be exactly the same value used to configure the Webex Integration Redirect URI. Note case sensitivity and port restrictions.

Optional.  File system location where the certificate key is stored.

Specify the password for the file that contains the certificate keys.

Certificate chain (or Chain of Trust) is made up of a list of certificates that start from a server's certificate and terminate with the root certificate. If your server's certificate is to be trusted, its signature has to be traceable back to its root CA.

Mandatory.  Timestamp of the earliest WebEx recording to be ingested. This can be a timestamp in the past, e.g., 2020, if historic Webex content is required to be ingested.

The Import Source will gradually catchup with real-time as it is run by successive Data Management Policies, but will take longer to catch up depending on the number of historic recordings, the Maximum Recording Length and Availability Delay.  In the case of mass historical ingest, it is recommended to set the Maximum Recording Length to a large number, e.g., 999 and reduce the Availability Delay to a small number, e.g., 10 minutes.  Once the ingestion has caught up, adjust each of these parameters to their correct operational values.

Example:

2023.01.29 07:00:00

Mandatory.  Maximum length of Webex content to be ingested.  Content exceeding the maximum length may not be ingested or an alert generated.

Example: 60

Mandatory.  Maximum time the import source waits for a Webex meeting to become available for ingestion.  If the meeting is not available after this time, it may not be ingested or an alert generated.

Optional.  Allows VFC to become the single repository for Webex content.

The recording deleted from Webex cannot be recovered, so this setting must be set with great care.

If a Compliance Officer deletes another user's recording, the recording will be inaccessible to regular users (host, attendees and shared), but will be still available to the Compliance Officer.

Only recordings of meetings hosted by the authenticated user can be deleted.

Mandatory.  Webex Authentication cannot be completed unless the VFC Import Source is running because it depends on an OAuth HTTP(S) callback from Webex to the Import Source. This is why the VFC Import Source must be saved and an Active Data Management Policy created. The callback provides VFC with an Access Token that Webex content ingestion depends upon.

The Authentication Keep-Alive setting is a temporary configuration value which ensures the installation engineer has enough time to press the Authenticate Now button and authenticate with Webex before the VFC Import Source terminates inline with the VFC Data Management Policy.

Once the engineer has completed Webex authentication, the Authentication Keep-Alive must be reduced to zero because the Access Token has been obtained and saved locally on the server where the VFC Import Source is run.  When the Authentication Keep-Alive value is changed, the Import Service must be restarted.  If the Authentication Keep-Alive is not set to zero and the import source is custom scheduled, it will not increment the Webex time boundary sliding window, so after the initial ingestion, no further content will be ingested.

The Access Token is securely encrypted. This value can be changed at any time during production hours. The updated value will be used the next time the Data Management Policy runs the Import Source.

Example:

99 - During initial installation

2 - If a periodic check of the VFC Webex Token/Authentication status web page is required during production.

0 - During normal operation to avoid delay in completing processing of the Import Source.  The value can be updated at any time if an adhoc check is required.

Mandatory.  Do not press this button until an active Data Management Policy has been created.

Until the VFC Import Source has been saved with settings for all of the above values and an active Data Management Policy created, this button will not authenticate the VFC Import Source with Webex and content will not be ingested.

Once authenticate now has been pressed, it should not be used except on the very rare occasion the integration has not been running for along time and the Webex Access Token has expired.