Invalid Redirect URL (4,700) on valid redirect url

[amalgamateimages (Rico)]

Hi Tommy am new to zoom. what the redirection url supposed to be …do i create that.?

[pcvetanov (Petar)]

Hi @tommy ,
I get the 4700 redirect error when I try to pass different subdomain to the install path.
My app’s name is Melon LMS.
As the docs say, I’ve specified https://any.melonlearning.com/oauth/zoomauth as my Redirect URL for OAuth and have set it as a whitelist URL (https://any.melonlearning.com).
What else should we do to support Multiple Environments ?
Thanks

[tommy (Tommy Gaessler)]

Hey @amalgamateimages,

Yes, you create it, but to test you can just use https://zoom.us.

Thanks,
Tommy

[tommy (Tommy Gaessler)]

Hey @pcvetanov,

Take a look at my two posts here and let me know if that helps:

Does zoom support more than two environments for oauth2?

Hey @tuancode, @michael.solomon, This is totally possible! Let me walk you through how to do this with the base domain of example.com For your whitelist, simply add your base domain: https://example.com Then in your dev/prod redirect url field, add a default redirect, https://any.example.com (this will be programmatically overridden to the correct sub domain, continue reading below) Now, with your install URL (the url mentioned in Step 1. of the OAuth guide) in your code, dyna…

'Invalid request : Redirect URI mismatch.' despite using ngrok

Hey @Nad, Let me know if this helps explain things: The Redirect URI needs to be the same URI from the authorization (install URL) through to the Get Access Token request. So with these URLs set: [Screen Shot 2020-07-23 at 10.02.37 AM] When I go to install the app from the “Activation” page, it defaults the redirect URI to the one specified in the “Redirect URL for OAuth” input: https://zoom.us/oauth/authorize?response_type=code&client_id=ztmR8sxaSBGZ66b5laR7Ag&redirect_uri=https://zoom.u…

Thanks,
Tommy

[pcvetanov (Petar)]

Thanks for the reply @tommy,
I’ve tried changing the “Redirect URL for OAuth” from https://any.melonlearning.com/oauth/zoomauth to my base domain https://melonlearning.com/oauth/zoomauth and whitelisting my new tenant https://melonlmstraining.melonlearning.com , but again I get the 4700 error when trying to initiate the OAuth flow from https://melonlmstraining.melonlearning.com. The original address https://melonlms7.melonlearning.com/ works without any issues.
Note that the https://melonlmstraining.melonlearning.com was whitelisted after the app was published (I tried to Regenerate the Publishable URL, as I’ve read this might help, but it had no effect).
Attaching screenshots of my Whitelist URLs

and the 4700 error

[tommy (Tommy Gaessler)]

Hey @pcvetanov,

Can you try moving your state query param to before the redirect uri? Like this:

authorize_url?client_id=asdfasdf&state=asdf&redirect_uri=https://zoom.us

Let me know if that works!

Thanks,
Tommy

[jeffatpresence (Jeff)]

@tommy Can you validate something for me? I was approved last Thursday for using the production install link for beta users until our app submission is approved. I received an email on Friday stating that the submission requires further information to be approved and now a beta user cannot use the install link.

Are we not allowed to use the production install link now that app has to be resubmitted?

I looked at the Submit portion of my app and it appears that my publishable URL should work. So something isn’t making sense

The app name is Presence and the redirect uri that I’m using is https://richmond.presence.io/admin/zoomauth which matches and was working last week.

[tommy (Tommy Gaessler)]

Hey @jeffatpresence,

Are you seeing an error / cannot install outside account message when a user is trying to install your app? If so, can you share a screenshot?

Thanks,
Tommy

[jeffatpresence (Jeff)]

I’m getting the same error mentioned in this thread, invalid redirect 4700. It was worked for awhile and we noticed that it wouldn’t work today. So I was wondering if that was tied to me app being rejected for it’s initial submission.

[tommy (Tommy Gaessler)]

Hey @jeffatpresence,

What is the name of your app? It should not be connected to an app publish rejection.

Thanks,
Tommy

[jeffatpresence (Jeff)]

My post above has my details. The app name is Presence.

The redirect URL specified in marketplace:
https://any.presence.io/admin/zoomauth

The redirect URL that is not working (and none others are working):
https://zoom.us/oauth/authorize?response_type=code&client_id=<PRODUCTION_ID>&redirect_uri=https://richmond.presence.io/admin/zoomauth

The production client Id was removed but we are using what’s specified in the publishable URL.

[michael3 (Michael)]

I’m also getting the same invalid redirect 4700 message. My app, named Continu, has been published for a while and had many subdomain integrations. The only difference I can find with the reported error is that the subdomain is only 2 characters, but I don’t see why that would have any affect.

[tommy (Tommy Gaessler)]

Thanks @michael3, @jeffatpresence,

We believe this to be a bug, and are currently investigating the issue.

-Tommy

[tommy (Tommy Gaessler)]

Hey @jeffatpresence, @michael3, @pcvetanov,

It should be fixed now!

Please try and let me know if you see any issue.

-Tommy

[michael3 (Michael)]

Thanks @tommy! This appears to be resolved on my end.

[jeffatpresence (Jeff)]

It’s working for me now as well. Thanks so much for the help!

[tommy (Tommy Gaessler)]

Hey @jeffatpresence, @michael3,

You are welcome! Apologies again this happened!

Thanks for building with Zoom!

-Tommy

[pcvetanov (Petar)]

Hi @tommy,

Thanks for the suggestion - moving the state param outside the redirect_uri did the job and I can now get oauth code and exchange it for an access token. Many thanks once again!

[tommy (Tommy Gaessler)]

Great! You are welcome!

Thanks,
Tommy

[dayo]

Hello,

I’ve read this thread because I am having the same issue. I have just added a new Whitelist Url on a Published app, but I’m getting the Invalid Redirect URL when trying to authorize over this new URL.

The last message from @tommy on Aug 11 suggests a bug was fixed, but I am still experiencing the issue. It seems to work with the Development version of the app but not with the Production version.

The app name is: Breeio

Any help would be greatly appreciated.

Kind regards,

Dayo.