We have a beta feature where we turn on registration for our clients’ meetings, so that we can get contact information into zoom which can then be surfaced by the API. We do this by looking for upcoming scheduled meetings using the zoom API, and then flipping the registration flag on.
When the host clicks on the link to the meeting from their calendar, it first goes to the web browser to authenticate them. If they are not already logged in to the zoom UI in the web browser, it takes them to the registration page. If they click register from the registration message, it blocks them with an error message: “Host cannot register”, and doesn’t provide any workaround. This is the first bug - since they are clicking on the link from their own calendar, it shouldn’t take them to registration. Arguably, users shouldn’t even need to be signed into the web browser in order for the initial link to work.
We encourage our users to sign into the web UI with “remember me” checked, to work around this. The problem is that some subset of our users get logged out after around 24 hours, even with “remember me” checked. That means that they get blocked when trying to sign into their meetings, using the calendar link. This is the second bug.
Bug 1) Hosts who click on the meeting link from their own calendar, when meeting is required, get bumped to the registration page when they are not logged into the browser. Registration page will not admit them to the meeting.
Bug 2) Subset of users get logged out from web browser, even if they have “remember me” checked.
Which App Type (OAuth / Chatbot / JWT / Webhook)?