We have a large number of students who join Zoom meetings directly inside our app using the Meeting SDK. We also have many instructors who use their own Zoom accounts to host sessions for those students.
Everything was working correctly, but suddenly it stopped working. Students can no longer join meetings inside our app, even though nothing has changed on our side.
If your use case cannot support implementing OAuth to obtain these tokens, an exception may be available — but whether it applies depends on your specific situation and reasoning. To have it evaluated, please submit your app with the “Request Anonymous Join Exception” toggle enabled under Features > Embed > Meeting SDK, and include a clear explanation of your use case in the provided text field.
Hi, @yoon.conner@chunsiong.zoom currently I encounter the same issue: the user can’t join meetings from an external account. My app is using the General App instead of the SDK or OAuth app. When I tried to add a scope, I only found user:read but I can’t find user:read:token scope for my app.
Also, how can I test the implementation of the OBF token on my Development environment since an external account can not access my app in the development environment?
@chunsiong.zoom Which scenario are you referring to? For getting the new scope `user:read:token` to appear on my app scope, or external account can acces my app?
@simudin the application must be published for external account join. In addition to publishing, you need to make sure you are using OBF token in the SDK as part of the join parameters. If not you will not be able to do external account join.
@simudin no it should not. Do note after selecting the additional scopes, the application will need to go through review and approval process again for newly selected scopes to take effect.
It will not affect the existing approved app during this process.