Web Meeting SDK 2.3.0

Announcements New Releases
1

Hello Zoom Developers, here are the updates for the Web Meeting SDK version 2.3.0 release :

Added

  • Support to use SDK key and secret to generate tokens to join meetings.

Using SDK key and secret to generate tokens to join meetings

Now you can use an SDK App type to generate Web Meeting SDK Signatures. The signature also works to authenticate with the Native Meeting SDKs. To do so, follow the instructions in Generate Signature, except use the following:

const KJUR = require('jsrsasign') // https://www.npmjs.com/package/jsrsasign
const crypto = require('crypto') // crypto comes with Node.js

function generateSignature(sdkKey, sdkSecret, meetingNumber, role) {
  // Prevent time sync issue between client signature generation and zoom 
  const iat = Math.round(new Date().getTime() / 1000)
  const exp = iat + 60 * 60 * 2

  const oHeader = { alg: 'HS256', typ: 'JWT' }

  const oPayload = {
    sdkKey: sdkKey,
    mn: meetingNumber,
    role: role,
    iat: iat,
    exp: exp,
    appKey: sdkKey, // required if using signature for Native SDK
    tokenExp: iat + 60 * 60 * 2 // required if using signature for Native SDK
  }

  const sHeader = JSON.stringify(oHeader)
  const sPayload = JSON.stringify(oPayload)
  const signature = KJUR.jws.JWS.sign('HS256', sHeader, sPayload, sdkSecret)
  return signature
}
// pass in your Zoom SDK Key, Zoom SDK Secret, Zoom Meeting Number, and 0 to join meeting or webinar or 1 to start meeting
console.log(generateSignature(process.env.ZOOM_SDK_KEY, process.env.ZOOM_SDK_SECRET, 123456789, 0))

See Authentication for a description of the other fields. The Web SDK will ignore the fields specific to the Native SDK and the Native SDK will ignore the fields specific to the Web SDK. Complete documentation about this feature is forthcoming.

Enhanced

  • Overall video quality of service when in poor or lossy network conditions.

Fixed

  • Issue where the Chrome browser version was not correctly read if it were greater than version 100.

Client View

Added

  • Support for account, group, or user-level settings for controlling webinar chat settings and permissions.
  • Support for smart gallery view for Zoom Room devices.
  • A message in the developer console about SharedArrayBuffer (SAB) and removed the end-user notification that recommended that users upgrade to the latest version of Chrome and SAB.

Enhanced

  • Overall quality of service for video streams.
  • getBreakoutRooms API function signature to be consistent with other developer platforms. The format of the return value was changed, but the interface was not.

Fixed

  • New registration flow not correctly enforcing the tk token requirement for joining attendees.
  • Incorrect Japanese translations for certain words.
  • Issue where messages in chat history changed lines.
  • Issue where the Breakout room (BO) title changed lines.

Component View

Added

  • Support for resizing (documentation forthcoming).
  • Support for allowing the attendee to talk.

Enhanced

  • Ability to support Join Before Host and Waiting Room features simultaneously.

You can also see the update listed on our Changelog: https://marketplace.zoom.us/docs/changelog

Thanks,
Tommy

1 Like
3

@tommy
When will the patch 2.3.1 be available to fix the blocking React issue happening with the 2.3.0 ?

4

Hey @nvivot ,

Please see my comment here:

Thanks,
Tommy

5

Hello @tommy,

Support to use SDK key and secret to generate tokens to join meetings

Is this optional? Can we continue to use API Keys with 2.3.0 or it will not work with 2.3.0 anymore?

6

Hey @sudhamshu.n ,

Yes, you can still use API Key/Secret, but we recommend switching to SDK Key/Secret.

Thanks,
Tommy

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.