# Meeting without passcode despite user settings

**URL:** <https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224>\
**Category:** API and Webhooks\
**Created:** [October 5, 2020, 4:51pm UTC](https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224 "2020-10-05T16:51:01Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![hsintegration](https://avatars.discourse-cdn.com/v4/letter/h/54ee81/32.png) [@hsintegration](https://devforum.zoom.us/u/hsintegration)\
**Post date:** [October 5, 2020, 4:51pm UTC](https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224/1 "2020-10-05T16:51:01Z")

</div>

**Description**  
When waiting room is disabled (without a lock) and passcode is on (without a lock) in user settings then new meetings are created with waiting room enabled and no auto-passcode.

**Error**  
The API doesn’t take into account user settings and creates new meeting with passcode off but waiting room on.

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
OAuth

**Which Endpoint/s?**  
[Create new meeting for user](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate)

**How To Reproduce (If applicable)**  
Request body:

```
{
  "topic": "Test",
  "type": 2,
  "start_time": "2020-10-21T18:00:00Z",
  "duration": 15,
}

```

Response (no passcode/password and `"waiting_room": true`):

```
{
    "uuid": "6I3A+ch/THOguhLeWrVlHw==",
    "id": ****** ,
    "host_id": " ******",
    "host_email": " ******",
    "topic": "Test",
    "type": 2,
    "status": "waiting",
    "start_time": "2020-10-21T18:00:00Z",
    "duration": 15,
    "timezone": "Europe/Kiev",
    "created_at": "2020-10-05T16:07:46Z",
    "start_url": " ******",
    "join_url": " ******",
    "settings": {
        "host_video": false,
        "participant_video": false,
        "cn_meeting": false,
        "in_meeting": false,
        "join_before_host": false,
        "mute_upon_entry": false,
        "watermark": false,
        "use_pmi": false,
        "approval_type": 2,
        "audio": "both",
        "auto_recording": "none",
        "enforce_login": false,
        "enforce_login_domains": "",
        "alternative_hosts": "",
        "close_registration": false,
        "registrants_confirmation_email": true,
        "waiting_room": true,
        "request_permission_to_unmute_participants": false,
        "global_dial_in_countries": [
            "US"
        ],
        "global_dial_in_numbers": [
            {
                "country_name": "US",
                "number": "+1 3017158592",
                "type": "toll",
                "country": "US"
            },
            {
                "country_name": "US",
                "number": "+1 3126266799",
                "type": "toll",
                "country": "US"
            },
            {
                "country_name": "US",
                "number": "+1 3462487799",
                "type": "toll",
                "country": "US"
            },
            {
                "country_name": "US",
                "number": "+1 6699006833",
                "type": "toll",
                "country": "US"
            },
            {
                "country_name": "US",
                "number": "+1 9294362866",
                "type": "toll",
                "country": "US"
            },
            {
                "country_name": "US",
                "number": "+1 2532158782",
                "type": "toll",
                "country": "US"
            }
        ],
        "registrants_email_notification": true,
        "meeting_authentication": false
    }
}

```

**Screenshots (If applicable)**

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/1/f/1f49cb971d2fbe5b5228e6067cd778db57d7f9f1.png)

**Additional context**  
After playing with an API a bit, it looks like the use case falls into Scenario 6 - [https://marketplace.zoom.us/docs/guides/stay-up-to-date/announcements#api-behavior-changes](https://marketplace.zoom.us/docs/guides/stay-up-to-date/announcements#api-behavior-changes). Still weird the API ignores user settings.

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 6, 2020, 3:28pm UTC](https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224/2 "2020-10-06T15:28:52Z")

</div>

Hi @hsintegration,

Based on your use case, it does sound like this is our Scenario 6 outlined [here](https://marketplace.zoom.us/docs/guides/stay-up-to-date/announcements#api-behavior-changes):  
 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/0/40a6db272be5900c1a1bcf53a0fdf6b4e432a2a1.png)

While this is expected behavior, I do appreciate the feedback that this may seem a bit unexpected. If you have further questions about any of these scenarios, just let me know.

Thanks,  
Will

---

<div class="post-metadata">

**Author:** ![hsintegration](https://avatars.discourse-cdn.com/v4/letter/h/54ee81/32.png) [@hsintegration](https://devforum.zoom.us/u/hsintegration)\
**Post date:** [October 7, 2020, 11:28am UTC](https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224/3 "2020-10-07T11:28:33Z")

</div>

Hey @will.zoom,

Thanks for looking into this.

Users of my application create lots of meetings and they are a bit confused with the way it works right now, so I’m looking for a way to create meetings that correspond user settings.

I’ve tested the API and it looks like I’ll have to generate password on my end and pass it to Zoom via request. This means I need to follow passcode requirements. Can you please clarify what are the passcode restrictions/requirements to fulfill _“Use enhanced weak passcode detection”_ and what will happen if a passcode didn’t pass it?

Thank you,  
Alex

---

<div class="post-metadata">

**Author:** ![hsintegration](https://avatars.discourse-cdn.com/v4/letter/h/54ee81/32.png) [@hsintegration](https://devforum.zoom.us/u/hsintegration)\
**Post date:** [October 7, 2020, 1:27pm UTC](https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224/4 "2020-10-07T13:27:43Z")

</div>

Also, could you please advise if there is a way to check if waiting room or meeting password settings are locked in account settings? So that we can check if a particular user settings conform scenario 6?

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 8, 2020, 5:20pm UTC](https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224/5 "2020-10-08T17:20:06Z")

</div>

Hey @hsintegration,

Can you clarify what setting you’re referring to when you reference “_Use enhanced weak passcode detection_”?

In reference to checking a user’s password/waiting room settings, this can be retrieved via this endpoint:

> **[Get User Settings - Users - Zoom API - API Reference](https://marketplace.zoom.us/docs/api-reference/zoom-api/users/usersettings)**
>
> Retrieve a user's settings.
> Scopes: user:read:admin user:read
> 
> Rate Limit Label: Medium
> 
> Authorization
> 
> Flow: authorizationCode
> 
> Authorization URL: htt...

And if you have admin privileges, you can use this API to get an account’s settings:

> **[Get Locked Settings - Accounts - Zoom API - API Reference](https://marketplace.zoom.us/docs/api-reference/zoom-api/accounts/getaccountlocksettings)**
>
> Account Locked Settings allow you turn settings on or off for all users in your account. No user except the account admin or account owner can change th...

Best,  
Will

---

<div class="post-metadata">

**Author:** ![hsintegration](https://avatars.discourse-cdn.com/v4/letter/h/54ee81/32.png) [@hsintegration](https://devforum.zoom.us/u/hsintegration)\
**Post date:** [October 9, 2020, 3:00pm UTC](https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224/6 "2020-10-09T15:00:30Z")

</div>

Hey @will.zoom,

> [@will.zoom](#):
>
> Can you clarify what setting you’re referring to when you reference “ _Use enhanced weak passcode detection_ ”?

“Enhanced weak passcode detection” is configurable via [account settings](https://zoom.us/account/setting):

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/1/4/14b4e358131fd36b6c526e8b4d51430eadc206c1.png)

I wonder if weak passcode detection can deny meeting creation through API call if the passcode is considered weak? If so, can you please clarify what passwords are not “weak”?

> [@will.zoom](#):
>
> [Get Locked Settings - Accounts - Zoom API - API Reference](https://marketplace.zoom.us/docs/api-reference/zoom-api/accounts/getaccountlocksettings)

Awesome, that is what I was looking for!

Thank you,

---

<div class="post-metadata">

**Author:** ![will.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/will.zoom/32/14417_2.png) [@will.zoom](https://devforum.zoom.us/u/will.zoom)\
**Post date:** [October 12, 2020, 5:15pm UTC](https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224/7 "2020-10-12T17:15:15Z")

</div>

Hey @hsintegration,

Ah, I see—Thank you for clarifying! If you still have questions about the criteria for enhanced weak passcode detection, please direct this query to our [Support Team](http://support.zoom.us), as they’ll be best suited to assist.

Let me know if you have any other questions I can help with though!

Best,  
Will

---

<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:** [November 12, 2020, 3:15am UTC](https://devforum.zoom.us/t/meeting-without-passcode-despite-user-settings/32224/8 "2020-11-12T03:15:22Z")

</div>

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