I have an app( called Xplan) that uses OAuth authorization and it is deployed to multiple servers. Each instance of the app has its own subdomain. There are over a thousand such subdomains, and it is not a static list.
To use our Zoom-Xplan app, users need to have an Xplan account and login to the site this account belongs to. If a new user comes to Xplan, the process is requesting a call rather than sign up by themselves.
We are currently preparing to submit the app. Could you guide us about all the possible approaches for installing process?
Thanks for your help.
Because our product is not a self-service account creation product, the user can not create an account on the landing page, if we use this introduction and request call page as the landing page, will it meet the Zoom app submission requirement?
Just so we are on the same page, the landing page is referring to some place on your site, which can be the users profile page for example. There you can show a button to connect with Zoom, which will kick off the OAuth flow. This flow is acceptable to be published on the Zoom App Marketplace.
Hi @tommy, to clarify, different users will be linked to different subdomains of our app. There is no single domain where all users can be redirected to start the OAuth flow. So having a single landing page for everyone doesn’t work out of the box. One way to overcome this would be take users to a common landing page and ask them to enter their specific subdomain to continue the authorization, similar to how Slack does it.