Hello, please help me to answer my questions. Our current scenario is to integrate the zoom sdk in our own app, so that users in our own system can initiate video conferences. When users log in to our own app, they need to create a zoom user together to call the zoom API. After the creation, they will be bound to users in our own system. Next time users log in to our app, they will also use the previously created zoom account, When calling Create users, which of the four types of actions do I need to use: create, autoCreate, custCreate, and ssoCreate?
Welcome to the Zoom Developer Forum, @906416121. Great use case and questions! We are excited to help you implement the desired workflow in your Application. Based on the details, I’d like to first clarify the feature/login benefits available for the users created from actions of Create, AutoCreate, CustCreate & SSO Create.
Create: The login information such email/password, needs activation
autocreate: user and password are set on request, no activation process,
custCreate: has no login, must be an ISV partner
SSO create: user, is created, and logins in via SSO IDP, no activation needed
create: The user will get an email sent from Zoom. There is a confirmation link in this email. Users will then need to click this link to activate their account for the Zoom service. The user can set or change their password in Zoom. (The same as adding a user via Zoom interface instead we doing it through API)
autoCreate: This action is provided for enterprise customer who has a managed domain. This feature is disabled by default because of the security risk involved in creating a user who does not belong to your domain without notifying the user. (It will automatically create a user in your account without the user acknowledging the confirmation email.)
custCreate : (has no login) This action is provided for API partners only. Users created via this option do not have passwords and will not have the ability to log into the Zoom Web Portal or the Zoom Client. This is usually created when a developer wanted to have a user that has one-time access to zoom just for the sake of creating a meeting. Remember that meeting cant be created without a host. These users can still host and join meetings using the start_url and join_url respectively. To use this option, you must contact the ISV Platform Sales team at isv@**zoom.**us.
Zoom uses Just-In-Time (JIT) provisioning with Single Sign-On by default. This means that when a user tries to login, a Zoom account will be created for them based on your SAML mapping. However, if you do not want Zoom accounts to be automatically created when a user attempts to sign in, you can use pre-provisioning instead. Pre-provisioning will need to be enabled by Zoom support. Pre-provisioning will require you to add new users via REST API or by uploading a CSV. Note :
In line with the above, SSO create, in the portal, to have this option, you need to have SSO set, prior to signing. I believe SSO creation via API can be done straight up.
When pre-provisioning is enabled for your account, the ssoCreate API call will also be enabled for your account. With this provision you will have to create users in advance for them to be able to login. Users created in this way has no password. If the user is a Licensed user, the API call will generate a Personal Vanity URL using the user name (no domain) of the provisioning email. If the user name or PMI is invalid or occupied, it will generate a random number/random personal vanity URL. Learn how to add users via REST A
This article covers:
- Zoom account with SSO configured
- Account owner permissions
Please let me know if this helps or if you have any additional questions.
Thank you for your answer. According to our scenario, I think I need custCreate. There are two questions about custCreate that I need your help with:
Can the users created by custCreate be used all the time? Or can it be used only once? I don’t want to create new users every time. I need users to bind to our system users after creation. The next creation meeting does not need to create new users. In addition, how many users can be created at most by using custCreate to create users?
Contact the isv team to use custCreate. What information does the content of the email need to help you try it out? For example, account information?
@906416121 Yes, can you use the custCreated user all of the time.
You can create users individually as well as with a batch request.
- Contact the isv team to use custCreate. What information does the content of the email need to help you try it out? For example, account information?
With regards to the information, you can simply provide general information about the use case and account details. Someone from the ISV team will then reach out to you with the next steps.