Dynamic Multi-Account Configuration for Zoom Webinars

Previously, the platform used a single pair of global Zoom credentials to process and embed all videoconferences within the Shocklogic systems. This created security limitations with Zoom, which prevented attendees from joining meetings or webinars created by Zoom accounts not owned by Shocklogic.

To resolve this and provide full flexibility for each event, a multi-account architecture has been implemented. Each client or project can link their own Zoom developer credentials. In this way, the platform connects natively using the organiser’s licence, allowing any meeting from their organisation to be embedded without security restrictions.

Configuration

There are two new alphanumeric fields within the system configuration (specifically located at: Pl Parameters → Profile Parameters → Webinar Profile).These fields are :

1. Client ID: Public identifier of the app created in the client’s Zoom account Marketplace.

2. Client Secret: Secret password linked to the above identifier.

How does the integration work?

The connection between Shocklogic and the Zoom Meeting SDK protocol is triggered when the attendee presses the button to enter the webinar screen:

• Local Verification: The system checks whether the administrator has filled in the Client ID and Client Secret fields for a specific project.

• Secure Signature: If these keys are found, the system generates an encrypted authentication signature using the organiser’s original credentials. The Zoom meeting will open seamlessly and transparently for the user.

• Automatic Fallback: If these fields are left blank or not configured for the project, the platform will automatically use Shocklogic’s default global credentials. This is particularly useful for events where clients do not have their own Zoom accounts.

How to use the new configuration?

To correctly configure custom credentials for a new event, the administrator should follow these steps:

1. Obtain the keys in Zoom: The organiser or client must log in to their administrator portal in the Zoom App Marketplace using the account that owns the meeting.

2. Create the application (Meeting SDK): A new application must be created. Note: It is not necessary to submit the app for review or “publish” it; keeping it as a private app is sufficient, as the system only requires authorisation to access its own meetings.

3. Copy the keys (App Credentials): From the application tab in Zoom, the client must copy their SDK Key (Client ID) and SDK Secret (Client Secret).

4. Configure the link in Shocklogic: Go to the project configuration at Parameters → Profile Parameters → Webinar Profile. In the field URL Webinar Complete Video, paste the full Zoom meeting link.

5. Paste the keys: On the same screen, locate the newly added fields Client ID and Client Secret, and paste the corresponding codes provided by the client in step 3.

6. Save: Save the changes made to the profile.

From this point onwards, when participants click to join the encrypted webinar within Shocklogic, the system will automatically orchestrate access using the direct resources of the meeting owner’s licence.