question Not able to generate OAuth 2.0 Token for Zoom in ServiceNow AI Platform forum

Not able to generate OAuth 2.0 Token for Zoom

Abhrajyoti Kan1 — Thu, 05 May 2022 17:53:32 GMT

I am trying to integrate zoom for creating meeting links with ServiceNow which uses OAuth 2.0 as authentication. But when I am trying to create an OAuth token with the "Get OAuth Token" UI Action, it shows the below error.

The authentication details are shown below.

Application Registries:

OAuth Credentials:

OAuth Entity Profile:

Re: Not able to generate OAuth 2.0 Token for Zoom

Tony Chatfield1 — Thu, 05 May 2022 21:12:28 GMT

Hi, have you white listed your redirect URL in the Zoom account that you are testing with?

Re: Not able to generate OAuth 2.0 Token for Zoom

Shreya Shah — Fri, 06 May 2022 06:46:58 GMT

You can use the Zoom Spoke - https://docs.servicenow.com/bundle/sandiego-application-development/page/administer/integrationhub-store-spokes/concept/zoom-spoke.html and follow instructions on https://docs.servicenow.com/bundle/sandiego-application-development/page/administer/integrationhub-store-spokes/task/setup-zoom.html to setup the connection for spoke instead of creating your connection from scratch in a separate application.

You have various ready available actions for Meeting Management and other categories.

Re: Not able to generate OAuth 2.0 Token for Zoom

Richard Hine — Fri, 06 May 2022 07:53:37 GMT

Hi, there is mention of this on the Zoom forums: https://devforum.zoom.us/t/invalid-redirect-url-4-700-on-valid-redirect-url/15049

Initial thing to try is as @Tony Chatfield says to whitelist your redirect URL in zoom, if that doesn't work then it is best to raise a support ticket with Zoom.

Re: Not able to generate OAuth 2.0 Token for Zoom

Abhrajyoti Kan1 — Mon, 09 May 2022 17:17:00 GMT

Hi @Tony Chatfield

Are you asking to whitelist the redirect URL like below?

Added the Redirect URL like the above image, but still getting the same error message.

Re: Not able to generate OAuth 2.0 Token for Zoom

Tony Chatfield1 — Mon, 09 May 2022 23:38:25 GMT

I have not configured a zoom integration so cannot advise where to configure,
but the majority of similar zoom integration issues found in an internet search suggest whitelisting is required\the potential solution for your issue.
Perhaps this is a question best answered by Zoom support forums.

Re: Not able to generate OAuth 2.0 Token for Zoom

Richard Hine — Tue, 10 May 2022 06:47:02 GMT

Perhaps check the URL I already posted for you https://devforum.zoom.us/t/invalid-redirect-url-4-700-on-valid-redirect-url/15049/41

This tells you where to add the whitelisting to Zoom which is different to the redirect URL.

Re: Not able to generate OAuth 2.0 Token for Zoom

dantadysak — Thu, 12 May 2022 12:32:48 GMT

I am having the exact same problem you are having. We setup ours yesterday and get the same issue on the Zoom setup side. We found the zoom forum white listing doc right away and it helped us get the setup saved on the zoom side but we still get the same error that you get. Also, when I hit "Get OAuth Token" related link in the OAuth 2.0 Credentials it shows me a login page to zoom and I think I should be seeing some kind of alphanumeric string but the SNOW docs are so vague on this. Let me know what you find out and I will pass on what I know if we make progress.

Re: Not able to generate OAuth 2.0 Token for Zoom

dantadysak — Fri, 13 May 2022 19:58:03 GMT

I got past the error code 4700 after we added out instance name and the redirect url on the white list but now I get a zoom login web page and not what I would expect. I would expect that when I click Get OAuth token it would return a token and the system would add it somewhere to track so it could trust the connection back and forth. I opened a SNOW support case since we tried this 2 times now and get the same results and do not know how to proceed.

Re: Not able to generate OAuth 2.0 Token for Zoom

Abhrajyoti Kan1 — Mon, 16 May 2022 20:16:51 GMT

Whitelisted the servicenow instance URL and it worked!

Thank you @Tony Chatfield @Richard Hine!