-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for creating a meeting using a default password #281
Comments
Makes a lot of sense to enable developers to request the password to be auto-generated. Also, I'm intrigued by this comment you made:
What happens if a developer attempts to create a meeting but does not pick any of the options? Do they get a clear error message from Zoom? If not, is this something we should validate in ZoomNet? FYI: my attitude regarding validation has been to avoid it as much as possible because who knows if/when the validation rules in the Zoom API change and I would hate to enforce some validation rule that makes sense today but may or may not still be valid in the future. Having said that, I'm willing to make exceptions if there are situations that cause confusion, unclear error messages, unexpected outcome, etc. |
I did some testing it seems if you try to pick none of the options it will force the waiting room option. For example if you send this request:
It ignores the |
Just passing by.... I noticed I have recently read something about this topic here: In the first paragraphs it explains the behavior that @mxswd mentions. Hope this helps ;) |
Thanks for the link. Sadly the original contributor never completed the PR. @LucasMetal would this functionality be useful to you? |
No, I don't need it (at least for now). Keep up the good work!! |
Note to those interested in this new parameter: it appears that a custom password you specify when creating a meeting takes precedence. This means that setting the new Also note that when you set this new parameter to true, Zoom will EITHER generate a random password OR use the default password configured in your user's security settings. It's not 100% clear to me what determines which of the two actions is taken. |
🎉 This issue has been resolved in version 0.83.0 🎉 The release is available on: Your GitReleaseManager bot 📦🚀 |
Awesome, thanks a lot for making the change. It will help a lot. |
You're welcome. I raised #374 to warn developers about the breaking changes and guide them to resolution. Hopefully my instructions are clear. |
When creating a meeting there are 3 security options, and you must pick at least one.
If you use the API to create a meeting these security options don't match the API 1-to-1, but rather you need to combine certain options to trick zoom into working the way you want.
It seems if you want:
You need to send a request with:
join_before_host
set to true.jbh_time
set to an integer.waiting_room
set to false.Admin's have an array of options to configure meeting password strength so the API provides a convenient
default_password
option so you don't need to lookup the account password options and generate one that matches those rules yourself.I'm basing this off the light amount of documentation on:
https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/meetingCreate
And significant testing on my side.
The text was updated successfully, but these errors were encountered: