Ask AI

Configure the Qumu Cloud connector

Connect with Qumu to import videos and publish captions

📢
Requirements: Enterprise plan
 

This article assumes that you have Administrator access to your Qumu account, and Superuser access to CaptionHub.

 

1. In Qumu

  1. Log into Qumu, via your <yourcompanyname>.qumucloud.com or the <yourcompanyname>.kulu.net login
  1. Click on the Administration button at the top right hand side of the page
  1. Click on "OAuth2.0" on the left hand side, under the Authentication subheading
    1. Notion image
  1. Click on the Create button
    1. Notion image
  1. In the Create client dialogue box, enter "CaptionHub" in the description field, and enter https://app.captionhub.com/platforms/qumu/videos/configure_auth in the Redirect URIs field. Hit "Add".
    1. 💡
      Note: If you use SSO, and therefore a different subdomain to app.captionhub.com, you will need to adjust this URL to use the appropriate subdomain, e.g. https://yourcompany.captionhub.com/platforms/qumu/videos/configure_auth
      Notion image
  1. Copy the ID, and click the "Create button".
 

2. In CaptionHub

  1. Navigate to the Connectors page, via the drop down menu at the top-right
  1. In the Qumu team domain field, enter your path you use to login in to Qumu, e.g. <yourcompanyname>.qumucloud.com or <yourcompanyname>.kulu.net
    1. Notion image
  1. Paste the ID you copied from Qumu
  1. Hit the "Update" button at the bottom of the page
  1. Now, return to the Dashboard, and test the connector by selecting “New project from ... Qumu Cloud”. If you have any problems, please raise a ticket with our support team.

Additional setup for automation

To configure automation with Qumu Cloud, there are a few setup steps that require support from Qumu. Please follow the instructions below.

  1. Request authentication credentials from Qumu Support Email Qumu.support@enghouse.com and request the following:
    1. “Please create a client and provide a JWT secret for a Server Authentication Integration.”

      Qumu Support should respond with a text file, see example below. This file contains two key pieces of information:

      • key: This will be used as your Client ID
      • jwtSecret: This will be used as your Dynamic Ingest Secret
        • ['The auto generated JWT secret is: {"client": {"key": "somekey", "description": "JWT secret for OAUTH2/UCG", "redirectUris": [], "tokenValidityTimeMs": 10800000, "jwtSecret": "somesecret"}}']

          Important:

      • Open the text file and extract/copy the values without quotes after key and jwtSecret.
      • For example:
        • key: "somekey" → use somekey as your Client ID, example shown in red above
        • jwtSecret: "somesecret" → use somesecret as your Automation Secret, example shown in blue above
  1. Specify the Qumu User ID for Automation
    1. Finally, you’ll need to enter the Qumu User ID of the user you want Automation to run on behalf of. This should be the Qumu Cloud ‘Username’ of the user, not the email address. To find this:

      • Look in the Username column for the correct value.
  1. Confirm the user account is local (Not SAML)

Please confirm with Qumu Support that the user account you plan to use is a local DB user, not a SAML-based user.

Note: In Qumu Cloud environments with SAML enabled, accounts may appear in the system that reflect SAML users, but these are not true local accounts. For automation to work, you need a real local user created directly in the Qumu Cloud database.

Notion image

Automations can now be set up by following our automation guide. You can choose to import all presentations from Qumu (from the point the integration is enabled), or if you prefer to import a subset of projects, please set up tags for automation using the guide below.

Using tags for automation

It is possible to set up an automation template to process a subset of videos from your Qumu account. This is done using “Tags” metadata. For this to work, you need to set up a metadata type called “Tags” in your Qumu Cloud account. This metadata type must be called “Tags” and be of type “Tags”. In order to assign this metadata attribute to your presentations, you also need to enable it for all relevant presentation types. The steps for doing this are as follows.

Creating a metadata type for Tags

  1. Log in to your Qumu Cloud account
  1. Click the “Administration” button on the top right of the screen
  1. In the left menu, under “Workflow”, click “Metadata Type Library”
    1. Notion image
  1. Click the blue “Create” button at the top
  1. Give the new metadata type Name “Tags” and Data type “Tags”. Note that any deviation from this naming will mean the process does not work.
    1. Notion image
  1. Click Create
 

Assigning the Tags metadata type to your presentation types

Now you’ll need to add this metadata field to each of your presentation types

  1. In the left menu, under “Workflow”, click “Presentation Types”
    1. Notion image
  1. For each presentation type you want to add tagging metadata for, click the pencil icon to edit
    1. Notion image
  1. In the Metadata section, click “Add”
    1. Notion image
  1. Select the Metadata Type “Tags”. Untick the other boxes, unless you want to show the tags to user.
    1. Notion image
 

Tagging a presentation

  1. In the presentation list, click the downward arrow and “Edit”
  1. In the “Info & Settings” tab, you should now see a “Tags” text box. Tags should be entered as a comma separated list.
    1. Notion image
  1. Click “Re-publish” to update changes

Setting up an automation template on CaptionHub to use tags

  1. Click your company logo/initials on the top right, and select “Automation” from the dropdown menu.
  1. Enter the name of your new automation template and click Create
  1. Select “Qumu” from Project source
  1. From “Automatically import”, choose “Tagged”
  1. Enter the name of the tag in “Filter by tags”
  1. Follow the steps to create an automation, as outlined in our automation guide

If you need help setting this up, please contact support@captionhub.com.

Did this answer your question?
😞
😐
🤩