Trouble using in-client OAuth silently (`authorize` API)

[donte.zoom (Donte)]

@tkishkin

Hi! I know it’s an old topic, but I have the same problem and the solution doesn’t work for me.

After my app is added via in-client auth, I detect that there are no saved tokens yet and make authorize call, which shows the consent screen again, even though the user context state is authorized. Which is a nuisance for the user.

At this point I haven’t called https://zoom.us/oauth/token yet (as I don’t have auth code yet), so I don’t understand how wrong redirect_uri could matter. Maybe someone could clarify?

Please see this post for solution for consent screen again even though the user context state is authorized:

In-client OAuth (`authorize` API) is not silent

Hi @donte.zoom , as I already mentioned in the community forum, a fix was found thanks to your suggestion. All I had to do was to add under “OAuth Allow Lists” the URL of the page from which the zoomSdk.authorize call was being made. In my case, https://zoom-cross-tenant.staging-linkando.com/zoomapp. Indeed, the documentation mentiones: "under the OAuth allow list section, add your app’s Home URL". The confusion in my case was due to the fact that my home URL redirects the user further to anot…