OpenID Connect (OIDC) is an authentication protocol built on the OAuth 2.0 standard that a Zoom user (desktop or web) can use to securely sign in. By configuring the app integration in Microsoft Azure AD endpoint’s implementation of OpenID Connect, you can add sign-in to Zoom via your AzureAD credentials, or, federated credentials if Azure
Configuring OpenID Connect (OIDC) Integration with Azure AD Read More »
User accounts, group memberships, and credential hashes can be synchronized one way from Azure AD (AAD) to Azure AD Domain Services (Azure AD DS or AAD DS). Azure AD DS integrates with your existing Azure AD tenant, which makes it possible for users to sign in using their existing credentials. Azure AD DS replicates identity
Connecting to Azure AD using Zoom LDAP Connector Read More »
Using the zm CLI (command line interface) it is possible to perform bulk actions such as: create user accounts in the Zoom server assign users to project vault assign users to role get all users mapped to a role get all users mapped to a project vault Basic syntax : zm -s zoom-server-url -c loadusers
Bulk User Account Creation, Project & Role Assignment Read More »
To integrate Okta as your IDP for Zoom Single Sign On (SSO) with user/group credentials stored on Azure AD, requires our OpenID Connect (OIDC) Connector to be enabled as well as LDAP protocol to pull the user attributes from Azure AD DS. Please check the prerequisites below before proceeding with the integration. Prerequisites An Azure
Configuring Okta (OIDC) with Azure AD Read More »
Camera cards from the various camera makers, such as Canon XF or Panasonic P2, have their own folder structures and file formats. Additionally, video files may be split into other smaller files that need to be recombined later. For example, Panasonic P2 cards often split audio and video into separate MXF files. Canon XF camera
Camera Card Workflows in Evolphin Zoom Read More »
These email messages are sent by Zoom for various events: Component Email about Can it be disabled? Configurable from Server activities and User Management Server Start No Modify the Bcc list in SMTP Settings (inside the Server Control Panel) from the Web Management Console. Server settings change through the Web Management Console No Modify
Mail messages sent by Zoom Read More »
The AI jobs are managed by the Hub Server, so you need access to the Hub Server to view the AI Jobs Dashboard. Access the AI Jobs Dashboard using the Hub Server IP at http://[HubIP]:8282/ The AI Dashboard is shown. It shows system information about the AI processes in Zoom. Click AI Jobs to see
After installing and configuring Hub, as soon as you are finished setting up your AI provider, configuration, and mappings in Zoom, your AI module in Zoom starts locating existing assets in the Zoom repository to be eligible for AI analysis. If any existing or new assets match your configured AI mapping rules, these are sent
From Zoom 7.3 onwards, zoom properties can be added through the Web Management Console. These are synced with other Zoom Server peers, Preview Servers, Curator Servers, and Zoom Clients. To add a property, follow these steps: In the Web Management Console, open the Server Zoom Properties page under the System node in the Admin Menu
Zoom Properties in Web Management Console Read More »
After setting up the Hub Server and configuring Amazon settings on it, we also need to configure detailed Amazon AI parameters in Zoom using the Web Management Console. We need to set Amazon as the AI Provider, provide configurations for AI engines, and then map AI rules to AI engines. Follow these steps: AI Providers
Configure Amazon AI in Zoom Read More »
Once you have configured Hub in Zoom and installed your Hub Server, you can add Amazon settings to it. Start the Hub Server where you want to run AI jobs. On this Hub Server, open the conf folder inside the Hub installation directory. Inside the conf folder, locate ai-spec.xml. ai-spec.xml will be created automatically on
Configure Amazon AI on Hub Read More »
After your VideoFX / VideoLX system is set up, you can also set up Aspera for automatic high-res file duplication based on pre-configured conditions. You will need to set up an Aspera High-speed Transfer Server and an Aspera Client / CLI as part of this setup. Components The interaction of the Aspera system with the
Setting up Aspera for file transfer Read More »
Zoom 7.5 comes with the capability to integrate with Artificial Intelligence (AI) providers to analyze files and media in Zoom, store the results from AI, make the results searchable, and display the results in an innovative UI. Data from AI engines can also be used to automatically run tasks based on certain triggers. You can
Getting started with AI Read More »
We need to enable AI in Zoom before beginning to configure it. Follow these steps to enable AI for the first time or to update the AI Settings later: Open the Web Management Console for your Zoom Server. Example: https://zoom-server:9443 Log in using your admin credentials. In the Admin Menu sidebar, click Server Control Panel under the System node. Click AI
Once you have configured Hub in Zoom and installed your Hub Server, you can add Veritone settings to it. Start the Hub Server where you want to run AI jobs. On this Hub Server, open the conf folder inside the Hub installation directory. Inside the conf folder, locate ai-spec.xml. ai-spec.xml will be created automatically on
Configure Veritone AI on Hub Read More »
After setting up the Hub Server and configuring Veritone settings on it, we also need to configure detailed Veritone AI parameters in Zoom using the Web Management Console. We need to set Veritone as the AI Provider, provide configurations for AI engines, and then map AI rules to AI engines. Follow these steps: AI Providers
Configure Veritone AI in Zoom Read More »
The Hub writes its events to a log file ejh_server.log. This file is saved in the logs folder inside your Hub installation directory. Apart from ejh_server.log, wrapper.log is another log file present in the logs directory. The wrapper.log file logs any errors that were not logged in the Hub logs, including logs generated when the
The Hub Server handles archive/restore processes for Zoom version 7.3 onwards when configured as part of a Hierarchical Archive system on Zoom. It needs to be configured on Zoom first and also installed on a server machine later. The Hub Server’s configuration can be managed through Zoom’s Web Management Console. This guide will cover: Hub
Managing Hubs in Zoom Read More »
Hierarchical Archive allows multi-level archiving to be implemented in Zoom. An asset can independently move between different tiers of the hierarchy as configured for the system. You need to set up a Hub Server for this to work. The Hub manages the jobs that move assets between tiers and provides reports for the admin users.
Getting started with Hierarchical Archive Read More »
While enabling Hierarchical Archive we need to also enable Basic Archive on Zoom, if it is not already done. Follow these steps to enable Hierarchical Archive after setting up basic archive: Open the Web Management Console for your Zoom Server. ex. http://localhost:8443 or http://<zoomserver>:8443 Log in using your admin credentials. In the Admin Menu sidebar, click Server Control Panel under the System node.
Hierarchical Archive Settings Read More »
