We are using the REST API to create a Zoom meeting and then having users join the meeting using the join URL that is passed back after creating the meeting. For some reason everyone who joins the meeting is given the name of the host. So if the name attached to the userID used to create the meeting is “David” then everyone in the meeting is given the name “David” under their video/audio stream. The users can rename themselves, but it’s not ideal. This remains the case even when users who are joining the meeting have Zoom accounts and are logged in with their own name setup.
Here is the data we are using to create the meeting through the API, if that makes any difference. We are not setting the name of the user anywhere in this meeting creation so I am not sure what else to try:
Here is a screenshot showing two users in a call, both with the name set to “Courtney Williams.” Courtney is the user account that was used to create the meeting, using the endpoint "https://api.zoom.us/v2/users/" + zoomUserId + "/meetings"
We have tried this with up to 5 participants, all who have the Zoom client installed and logged into their own individual zoom accounts. Everyone who joins the meeting gets this same name.
We have also tried this with different accounts. I tried creating meetings with the Zoom account we use to develop our Zoom marketplace app, as well as a separate Zoom account that we use for account services and they both have the same issue. It always names everyone in the call the same name as the user that was used to create the meeting.
Thank you for patiently waiting. Our developers are still trying to fix the issue. As of now we do not need any more information. I will update you once it is fixed.
When using the Zoom marketplace API to create a meeting for a user there are 2 URLs that get passed back for the meeting, start_url and join_url. When using the start_url to launch zoom anyone who clicks that link gets signed into the account of the user who created the meeting (or the user the meeting was created on behalf of through the API). After clicking that link and getting logged in automatically they are able to access the user’s Zoom settings and view all of their cloud recorded calls etc.
This doesn’t seem like the intended behavior, and looks like a security issue, but I can’t find much detailed information in the API documentation about how this is supposed to behave.
We no longer use this URL to launch meetings, but for a while it was essentially causing everyone who joined a meeting to single sign on into Zoom as the user who created the meeting and then they all had that user’s name in the meeting and had access to the user’s entire Zoom account through the browser.
We are aware of this issue, and I can confirm that we are releasing a new feature soon, which would be avoiding this. Although I do not have an exact timeline of when the update would be available, please follow our changelog to see the latest updates.
I know the original topic here is very old, but we’ve seen this behavior when you use the Start_URL instead of the Join_URL. The Start_URL appears to init the meeting as if it were being launched by the meeting owner, whereas the Join_URL doesn’t.