# Joining meeting timeout - Invalid parameter (Web SDK 2.4.5)

**URL:** <https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084>\
**Category:** Web\
**Tags:** webinar, web-meeting-sdk\
**Created:** [June 7, 2022, 1:37pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084 "2022-06-07T13:37:36Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![rohitbhargava](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rohitbhargava/32/28721_2.png) [@rohitbhargava](https://devforum.zoom.us/u/rohitbhargava)\
**Post date:** [June 7, 2022, 1:37pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/1 "2022-06-07T13:37:36Z")

</div>

**Description**  
How can I get 36 character length key for my zoom web SDK to pass into Zoom SDK console?

**Browser Console Error**  
When I click on join button on Zoom Join preview window? The error comes as  
**"Joining meeting timeout.**  
**Invalid parameter"**  
The dev tools window shows as SDK\_KEY length must be 36. However, in our Zoom Marketplace, we got JWT key of length 22 only.

**Which Web Meeting SDK version?**  
Zoom Web SDK v2.4.5  
_(can also be verified from console logs in the screenshot)_

**Meeting SDK Code Snippets**

```auto
// it's option if you want to change the WebSDK dependency link resources. setZoomJSLib must be run at first
  // ZoomMtg.setZoomJSLib("https://source.zoom.us/2.4.5/lib", "/av"); // CDN version defaul
  if (meetingConfig.china)
    ZoomMtg.setZoomJSLib("https://jssdk.zoomus.cn/2.4.5/lib", "/av"); // china cdn option
  ZoomMtg.preLoadWasm();
  ZoomMtg.prepareJssdk();
  function beginJoin(signature) {
    ZoomMtg.init({
      leaveUrl: meetingConfig.leaveUrl,
      webEndpoint: meetingConfig.webEndpoint,
      disableCORP: !window.crossOriginIsolated, // default true
      // disablePreview: false, // default false
      success: function () {
        console.log(meetingConfig);
        console.log("signature", signature);
        ZoomMtg.i18n.load(meetingConfig.lang);
        ZoomMtg.i18n.reload(meetingConfig.lang);
        ZoomMtg.join({
          meetingNumber: meetingConfig.meetingNumber,
          userName: meetingConfig.userName,
          signature: signature,
          sdkKey: meetingConfig.sdkKey,
          userEmail: meetingConfig.userEmail,
          passWord: meetingConfig.passWord,
          success: function (res) {
            console.log("join meeting success");
            console.log("get attendeelist");
            ZoomMtg.getAttendeeslist({});
            ZoomMtg.getCurrentUser({
              success: function (res) {
                console.log("success getCurrentUser", res.result.currentUser);
              },
            });
          },
          error: function (res) {
            console.log(res);
          },
        });
      },
      error: function (res) {
        console.log(res);
      },
    });

```

**Screenshots**

 ![zoomsdk1](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/d/5/d51324d7d27ef2a151a5ef4d4628ccd06d18c5a0.png)

**Device (please complete the following information):**

- HP Pavilion 15
- OS: Windows 10
- Chrome
- 102.0.5005.63

---

<div class="post-metadata">

**Author:** ![nvivot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/nvivot/32/4489_2.png) [@nvivot](https://devforum.zoom.us/u/nvivot)\
**Post date:** [June 8, 2022, 2:22am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/2 "2022-06-08T02:22:17Z")

</div>

@rohitbhargava

You should recreate an SDK type application, not a JWT application type. JWT is going to be removed in 2023 and should not be used anymore to generate credentials (jwt token) to access with the Web SDK.

By creating an SDK type app, you’ll get a 36 lenght key and the secret you need to generate your credentials, even for the web SDK.

---

<div class="post-metadata">

**Author:** ![rohitbhargava](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rohitbhargava/32/28721_2.png) [@rohitbhargava](https://devforum.zoom.us/u/rohitbhargava)\
**Post date:** [June 8, 2022, 4:16am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/3 "2022-06-08T04:16:59Z")

</div>

@nvivot  
I already have SDK type credentials which we use for Android/ iOS platforms.

I tried to use that key for webapp (utilizing Zoom WebSDK here) but every time it asks to log into Zoom, which shouldn’t happen with end-users.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [June 8, 2022, 7:05pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/4 "2022-06-08T19:05:38Z")

</div>

Hey @rohitbhargava

> [@rohitbhargava](#):
>
> I tried to use that key for webapp (utilizing Zoom WebSDK here) but every time it asks to log into Zoom, which shouldn’t happen with end-users.

Can you please share a screenshot of this page? If you could share more details about this specific issue including how to reproduce it that will help us provide a solution. 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![rohitbhargava](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rohitbhargava/32/28721_2.png) [@rohitbhargava](https://devforum.zoom.us/u/rohitbhargava)\
**Post date:** [June 9, 2022, 6:31am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/5 "2022-06-09T06:31:28Z")

</div>

Are there any restrictions based on (_account\_type_) who organizes the Webinars from Zoom account, _e.g., account\_type of owner, member, admin, etc_, for which it asks to log into Zoom first.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [June 9, 2022, 4:21pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/6 "2022-06-09T16:21:03Z")

</div>

Hey @rohitbhargava ,

It sounds like the webinar requires authentication to join:

> **[Webinars](https://marketplace.zoom.us/docs/sdk/native-sdks/web/client-view/webinars/)**
>
> The Zoom Developer Platform is an open platform that allows third-party developers to build applications and integrations upon Zoom’s video-first unified communications platform.

> **[Requiring authentication to join a meeting/webinar](https://support.zoom.us/hc/en-us/articles/4406604615693-Requiring-authentication-to-join-a-meeting-webinar)**
>
> If authentication profiles are configured by an admin, hosts can restrict meeting participants and webinar attendees to signed-in users only, and even further restrict it to Zoom users whose email ...

If you could share more details that would be helpful. 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![rohitbhargava](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rohitbhargava/32/28721_2.png) [@rohitbhargava](https://devforum.zoom.us/u/rohitbhargava)\
**Post date:** [June 15, 2022, 7:29am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/7 "2022-06-15T07:29:30Z")

</div>

@tommy Thanks for your response.

I checked it in our code. We have now used the SDK type key in place of the JWT type key (seeing that it will be deprecated by 01/2023) and with that, we have checked that if the Owner’s account hosts the Meeting, the login issue doesn’t occur.  
So, it confirmed that for SDK type, the meeting must be from the Owner’s account.  
Also, our issue is resolved for now.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [June 15, 2022, 4:58pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/8 "2022-06-15T16:58:38Z")

</div>

Happy to help @rohitbhargava ! 🙂

> [@rohitbhargava](#):
>
> So, it confirmed that for SDK type, the meeting must be from the Owner’s account.

FYI You can use OAuth now to start meetings that are not owned by the SDK account holder. Details here:

[https://marketplace.zoom.us/docs/sdk/native-sdks/auth#oauth-with-meeting-sdk](https://marketplace.zoom.us/docs/sdk/native-sdks/auth#oauth-with-meeting-sdk)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![rohitbhargava](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rohitbhargava/32/28721_2.png) [@rohitbhargava](https://devforum.zoom.us/u/rohitbhargava)\
**Post date:** [June 16, 2022, 10:51am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/9 "2022-06-16T10:51:26Z")

</div>

Hi @tommy Thanks for your response.

Can you share a few tutorials on implementing OAuth using Web SDK, so that we can try out on our project?  
The method provided above looks promising to tackle several use-cases faced while using JWT and SDK type credentials.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [June 16, 2022, 4:12pm UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/10 "2022-06-16T16:12:26Z")

</div>

Hey @rohitbhargava ,

Checkout our OAuth guide: [Zoom Developer Docs](https://marketplace.zoom.us/docs/guides/auth/oauth)

Let me know if that helps! 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [July 17, 2022, 2:12am UTC](https://devforum.zoom.us/t/joining-meeting-timeout-invalid-parameter-web-sdk-2-4-5/70084/11 "2022-07-17T02:12:32Z")

</div>

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