We decided to expand our app to another global region, to do this we added app.au.x.com to an already verified app.x.com app in zoom with Use Strict Mode for Redirect URLs turned off and Subdomain Check turned off.
However, when I try and use app.au as my oauth redirect Zoom simply says: Invalid redirect: https://app.au.x.com/blah (4,700)
So even though I am only redirecting to a subdomain it still wont let me.
Why is this?
Any change to a published Zoom app, including adding a redirect URL, requires resubmission and approval before it takes effect. Until approved, Zoom enforces your old configuration, so app.au.x.com gets rejected with error 4700 before the Subdomain/Strict Mode settings even come into play.
The error is happening because your published production app still has the old redirect URL config, but your code is already using the new redirect URL with the production client ID. These two are out of sync until the new version gets approved.
Resubmit the app for review with the new redirect URL added and it will work once approved. In the meantime, you can test it on your Development app version without needing review; just make sure to use the development auth URL and development client ID while testing.
Thanks,
Naeem Ahmed
To be clear it is not a “new” redirect URL, I am simply adding another region, so the original URL exists but I also want the new URL at the same time. I notice that I cannot actually do that due to the fact that only one production URL can be set at a time
Any change you make is still in development and not yet live in production, but your code is using the production client ID, which still has the old approved config. That is why it is failing.
Here are my suggestions:
For multi-region support, use a single common redirect URL in your Zoom app config and pass your tenant or region ID in the state parameter during OAuth. When Zoom redirects back, read the state on your backend and route to the correct regional URL from there.
Thanks,
Naeem Ahmed