OAuth Changes in Meeting SDK 5.9

Thanks Will. Based on your reply it sounds like we would need to go through the App Marketplace if we want to continue to offer login in our mobile apps. Here are some questions we have about the Marketplace submission process based on reading the documentation:

The Submission Checklist item 8 mentions providing a reauthorization event URL for testing. As we are a mobile app exclusively using the in-app Meeting SDK with no server-side component, how would this be handled? What is the expectation here for an app of our type?

Item 13 about specifying an installation process, what would be the appropriate installation process for a mobile app that has no server-side component? It seems that a mobile app does not neatly fit into the requirements for either “From Marketplace” or “From your landing page”. Also, is it OK that there would be no configuration URL as all configuration would occur within the mobile app?

Should there be a deauthorization link from the mobile app if the user has authenticated?

The security attestation seems to be targeted at web apps as opposed to mobile apps. What is the implication to answering no to any of the questions?

What would the effect be to our existing mobile app users if our app initially fails Marketplace submission?

Thanks!