Questions about published app install link of user managed Oauth app

API and Webhooks
#1

Hi, zoom masters, I have some questions before I integrate zoom into our applications.

Description
As I want to integrate zoom meeting functions into our web applications with each user’s zoom account. I am glad to see that zoom has supported subdomain for redirected URL of OAuth2 App. It quite meet our business since we provide each customer company a subdomain based on the same domain. Each subdomain is isolated include data of these subdomains。
Using Multiple Environments

Error
Based on this, as the develop document guidance I have to publish a user managed OAuth app to support this. is it correct?

I notice that there are two type to provide install link for outside users. From landing page and From marketplace. But AFAIK both of these two type should have a stable link that our customer could not to set their subdomain in redirect url or landing page. Just like https://zoom.us/oauth/authorize?response_type=code&client_id=7lstjK9NTyett_oeXtFiEQ&redirect_uri=https://sub1.yourapp.com
or landing page like https://sub1.yourapp.com/landing. So how could I build connection for outside zoom account with one of our customer register subdomain in our application and then save their authorization data under this subdomain and login user in this subdomain?

Which App Type (OAuth / Chatbot / JWT / Webhook)?
OAuth

#2

I notice that some other application provide a page to for user to set sub-Domain based on the landing page of their main domain. Is this the only solution for current zoom app integration? (user could not customized landing URL domain or redirect URL domain in install link when install zoom app)

#3

Hey @vince246,

When using multiple domains as part of our OAuth flow, you will need to update the redirect uri dynamically depending on the user and their respective sub domain—allowing an end user to set this on the landing page so that your app can ingest it and update the url accordingly would be one possible solution.

Let us know if you have additional questions about this. :slight_smile:

Best,
Will

#4

Hey @will.zoom, thanks so much for reply.
I have another question about support sub domain in OAuth before development. As document https://marketplace.zoom.us/docs/guides/auth/oauth#using-multiple-environments says:
If we want to support sub domain, we have to set redirect url as https://any.yourapp.com . I have some questions about this.

  1. I may want to know if this is a mandatory requirement when we want to support sub domain we have to add any in redirect url in app?

  2. Will below app setting also support sub domain in production app?

    redirect Url : https://yourapp.com
    whitelist : https://yourapp.com

    or

    redirect Url : https://anotherSubDomain.yourapp.com
    whitelist : https://yourapp.com

    https://zoom.us/oauth/authorize?response_type=code&client_id=******&redirect_uri=https://sub1.yourapp.com

    Seems in not published development app, it is also supported and Zoom not blocked this request. I tested it is only affected by whitelist.

  3. Based on 1 and 2, it affected us where to put subdomain setting page for outside user. If we add any in redirect url and app is install from marketplace mode, then the redirect url in install link seems also contains any.

#5

Hey @vince246,

Good questions, happy to clarify.

  1. You only need to specify any.domain if you need to support multiple sub domains. Otherwise, you can just pass the sub domain itself.
  2. This is supported in both dev and prod — to test in prod, make sure you’re installing the production instance of the app using the “Publishable URL” on the Submit tab of your app
  3. Have you tried directing users to your own landing page and having them enter their respective sub domain for you to ingest/update your URL dynamically based on user input?

Let me know if this helps :slight_smile:

Best,
Will

1 Like
#6

Hey @will.zoom, thank you for your answers. :smiley:

For 1 and 2, I am now clear. It is really helpful.
For 3, yes, I tried, landing page is a perfect solution, we could put more information to guide user. I asked because I am also considering that we could put user input subdomain page and login process (similar to landing page) on the redirect URL when redirect URL doesn’t contains subdomain or user is not logged in subdomain.

Anyway we will try both and find a more suitable implementation.

#7

Hey @vince246,

I’m glad to hear that Will resolved your issue! Please don’t hesitate to reach out if you encounter any further issues or questions.

Thanks,
Max

1 Like
#8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.