With the continuation of our 90 day Security initiative , we’ve released a new version of the Web SDK version 1.7.9. This additions to this version are ‘recaptcha feature for joining meetings’, ‘Rate limits for calling API Methods’ and enhancements such are ‘detailed error messages for troubleshooting’, and ‘enabling the WASM files to be downloaded before joining meetings’. For full details about the 1.7.9 release, please visit the latest Web SDK change log page . To get started, you can find the latest Web SDK version in the following locations: NPM: https://www.npmjs.com/package/@zoomus/websdk Sample Web App repo: https://github.com/zoom/sample-app-web Angular Sample App repo: https://github.com/zoom/websdk-sample-angular As Always #codeHappy

Hey @jerry, Thanks for sharing the use case. Disabling the recaptcha for your JWT App only disables it for meetings your Zoom account owns. We are disabling recatpcha for all accounts soon: [image] Web SDK - Upcoming Changes - Stay Up To Date - Documentation Web SDK Tentatively scheduled for August 10th 2020 @v1.8.0 New Additions Added support for Panelist and Host to join a webinar. Added support for j... -Tommy

I am still getting recaptcha when testing this. so seems it is not disabled. Can you answer the question regarding if all the customer’s that install the application from marketplace have to request disabled? Can we get all customers that are using our integration not need the captcha?

Hey @jerry, It will disable the recaptcha for joining any meetings that are owned / hosted by users on your account. Can you explain how your integration on the marketplace works with the Web SDK? Thanks, Tommy

The way it works is that our customers will install the integration using Oauth, meaning they will be hosting meetings under their account. Our customers that are using the integration all have their own customers that will be joining their hosted meetings using our platform. The customers that join these meetings, will only be able to join from their member portal, which requires them to authenticate to see the meetings they can join Since they already will be required to authenticate them self before they are presented with the meetings to join, they do not need to captcha since at that point, they are already determined to not be a BOT. By the way, you stated that you disabled captcha from my account, but we still are presented with Captcha now.

Hey @tommy, got a question if you don’t mind. For the rate limits, how does the 1 join request every 10 seconds work? Does that mean only one person can join a meeting every 10 seconds across all the meetings our API Key might be used for? If so, is there a way to increase that? Thanks!

I was literally about to ask this same question. @tommy To further add to this, are there limits to running 100’s of scheduled meetings at the same time under the same account? In our case, we’ll need to run several hundred meetings at the same allocated time slot, so for instance, 100 meetings at 9:00, then 100 meetings at 9:30 and so on. The meetings will not be created by the same User ID (each user will have a Basic Account under our main account), but it will be under the same main Account ID.

Hey @SimoneLabianca, @joshf, Please see this thread: [image] Rate limits on joining meetings/webinars? Web Hey @simon.ninon, The rate limit update is different from your issue. It is related to in meeting functions to prevent users from spam pressing buttons. For example, if someone calls the mute button over 10 time per second. The current rate limit is 5 p/s so we will disable the action. Thanks, Tommy Thanks, Tommy

Hey @jerry, We are working on a solution for the use case of hosting external meetings. As for closed caption on your account, are you hosting meetings owned by you (the meetings on the same account as the JWT Token)? Thanks, Tommy

We are not hosting meetings using the JWT token. All meetings will be hosted using OAuth, which our customers will be hosting, so we need all of our customers to be hosting their meetings without requiring Captcha.

Hi @tommy. We filled the opt out form for the captcha some time ago, but the captcha continues showing for our users. Any news about it, are you still reviewing the form applications? Thanks in advance, Santy.

Ya, we filled out the form 3 weeks ago to be whitelisted and have been told twice that we are…yet the captcha remains.

Web SDK version 1.7.9 is released!

Announcements New Releases

tommy (Tommy Gaessler (PM VDI, Web, Linux, & Meeting SDK)) July 29, 2020, 5:28pm 75

Hey @SimoneLabianca, @joshf,

Please see this thread:

Thanks,
Tommy

Topic		Replies	Views
SDK 1.7.9 - Recaptcha feature documentation Web	63	9113	August 10, 2020
Remove reCaptcha on webinars WebSDK1.7.9 Web	31	5831	August 12, 2021
Disable captcha Web	38	8844	August 14, 2020
Web SDK Updates version 1.7.10 New Releases	0	1937	July 8, 2020
Cannot join a meeting with the sample-web-app Web	8	2071	July 15, 2020

Web SDK version 1.7.9 is released!

Related topics