I came to this popular thread from a google search (as did many others) and wanted to create a new discussion about this since Zoom support closed that thread without any solution or even seemingly clearly understanding the problem we are facing as users.
Here is my use case. I have a four year old who has several different Zoom classes with URLs that change somewhat frequently. Despite the fact that she cannot yet read, I have empowered her to login to her class herself by showing her how to open the calendar and simply click the meeting link. For some of her classes, the teacher has sent me the correct password-encoded url to join the class. For others, I’ve been given a zoom link and a seperate password. The latter scenario creates too complicated of a situation: she’s not going to be able to type a password into a dialogue box when her class starts, and I’m not going to be able to tech support all of her teachers who don’t provide the password-encoded URL. Since I didn’t create any of these meetings, I also don’t have access to that URL from the Zoom meeting setup screens. I need a way to create a single password-encoded URL from the separate inputs of the meeting URL and the password.
In the previously mentioned How to generate join URL thread, the final message from a developer advocate seemed to assume that we need to either decode encoded passwords or understand how the passwords are encoded. But this is not the case at all. We simply need some way of being able to create a single password-encoded URL for a meeting when we already have both the meeting URL and the password. Security-wise, I don’t see why having both the URL and the password or the password-encoded URL as being any different. Either way, I’m able to access the meeting, but the password-encoded URL is much more convenient for myself and many others, who simply want to be able to click a link to start the meeting.
As an idea for one potential solution, without exposing any details of how these URLs are generated, Zoom could create a screen that would allow a user to enter the meeting ID and the password seperately and generate the URL for us and this whole problem would be solved.
As for how relevant this issue is, please observe that the original thread I referenced is the 4th most viewed topic in your API forum, with over 40K views. It’s also the only topic in the top ten in that forum that was shut down without any possible solution or workaround.
Zoom, please reconsider providing a viable solution for this issue.