We have a Zoom account where we have about half a dozen Zoom Marketplace apps published. One thing we want to do is implement SSO for more security and role-based access to our published apps, among other benefits.
One concern we have around enabling SSO is the requirement for a vanity URL. We have had mixed answers on whether using a vanity URL would cause a breaking change for our published marketplace apps, some saying yes, others saying they should be backwards compatible, so we are a bit confused.
What we’re trying to confirm is whether adding a vanity URL and enabling user SSO would impact our marketplace apps or not, and if so, whether it would be a breaking change or not. Any guidance on this would be helpful.
Can you clarify who is logging in to which intended account? Are you looking to add SSO login for the users on your account that develop/manage the app (not the Zoom users that use the app)?
Got it, and these users are on the developer account, separate from your main/corporate usage Zoom account?
Using the same SSO flow for two separate accounts would present a challenge. The Vanity URL will enable SSO for the main/non-developer account but would not be usable by the second/developer account.
This wouldn’t be breaking to the existing Marketplace apps, but it would present a login discrepancy between the two accounts.
The developer account would either need a separate vanity URL or would need to use another identity flow.
Thanks for confirming that this would not be a breaking change for Marketplace apps. Can we also confirm whether any action at all needs to be taken for our published apps?
As for the login discrepancy, I think this part should be fine. We have a separate email domain that users with access to the production account would be using that is separate from the domain we use for our corporate account. Our vanity URL would match this domain. Let me know if you still see any issues with this approach.