Meeting without passcode despite user settings

API and Webhooks
1

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

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
image1638×906 99.7 KB

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. Still weird the API ignores user settings.

2

Hi @hsintegration,

Based on your use case, it does sound like this is our Scenario 6 outlined here:
image

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

3

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

4

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?

5

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:

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

Best,
Will

6

Hey @will.zoom,

“Enhanced weak passcode detection” is configurable via account settings:

image
image880×744 52.1 KB

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”?

Awesome, that is what I was looking for!

Thank you,

7

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, as they’ll be best suited to assist.

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

Best,
Will

8

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