Zoom SDK web endpoint marked as 'http' by browsers

Description
I am having issues with running my SDK implementation on most OS’s including Desktop and mobile devices. The issues range from devices not being allowed (blocked camera, and blocked audio), to the application not even starting.

When I checked site settings I found out that the zoom endpoint was in ‘http’. This is supposed be ‘https’ in my opinion and is the reason for the devices not being allowed for the site/app.

Is there a walk around? Or I’m I missing something?

Which Web Video SDK version?
1.9.5

Screenshots
Screenshot from 2024-02-22 21-28-04

Hi @godwin.owonam ,

Are you running into these issues when testing with our sample application?

thanks,
Rehema

Hi @rehema.zoom
Thanks for responding.

The sample application was modified to suit our requirements and I believe that is the aim of having a sample application.

However, we hosted the application and we are using the hosted application (from a https server) in an iFrame on a webpage.

I don’t know if there is anything wrong with that (just informing).

I appreciate your feedback.
Please enlighten us where the source of the problem may be.

Thanks,
Godwin @godwin.owonam

Hey @godwin.owonam

The connection between the Video SDK and the Zoom server always requires the HTTPS or WSS protocol.

Could you please check if it’s your network policy (typically the proxy server) that is causing the switch to the HTTP protocol?

Thanks
Vic

Hi @vic.yang

After troubleshooting for some time, I find that the issue comes from the cookies used by zoom.us. It appears the SameSite attribute has not been set at all in the cookies. This should be the cause of the issue.

Hence, because the SameSite attribute is not set, the browser defaults it to ‘Lax’ and blocks the cookies, and the application cannot start.

Please see attached screenshots.

As you can see, below, these cookies are marked as affected cookies on the browser:

Hey @godwin.owonam

These cookies are unrelated to the functionality of the Video SDK; they simply record some preference settings on the Zoom website. Could you please take another look to see if any other reasons are causing HTTP-related issues?

Thanks
Vic

@vic.yang

Yes, you are right. The issue was related to CORS since our SDK was hosted in an IFrame provided in a domain different from our main domain.

Thanks.

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