Preparing an app for submission and stuck on “Direct Landing URL” for install.
We don’t have a singular publicly accessible install URL. We have many privately accessible install URLs.
We have built a custom integration to authorize and install the app with one step from within our client sites using oauth so we are unsure of what to put here.
I’m trying to accomplish the same thing as the OP and need some clarification.
I’m an engineer for a SaaS platform where each of my clients also has their own subdomain, e.g.: clienta.mysaas.com
Because of that, a single redirect uri doesn’t work because they authenticate within my app based on the subdomain.
What I need to do is allow the user to go to clienta.mysaas.com, login to my application and then click a button to install Zoom. So what I need to do from there is pass their subdomain clienta as a state query parameter so that the redirect_uri that I setup in my OAuth app now has a context of the client so it knows how to store access/refresh tokens for that particular client.
Does Visit site to Install accomplish that? Is it possible to do that?
EDIT: posted this in wrong thread, reposting here.
Thanks @tommy that helped me get one of my environments working.
I think I might need to make two apps to support my use case unless you can answer this problem too:
I have two versions of my application, the new one is a full rewrite with totally different URL scheme.