Clarification on OBF tokens and ZAK tokens (URGENT)

Meeting SDK
1

Hello Zoom.

I am trying to understand if we are affected or not.

We have an organization with 10,000+ real people using our product (mobile and web app) integrated with our product.

These people DO NOT have an existing Zoom account.

From what I know we use a ZAK + JWT flow, but we have a host’s Zoom account and a developer Zoom account where the SDK app exists and is currently hosted on the marketplace.

Will we need the OBF tokens or can we continue with ZAK + JWT flow.

I may need to get in touch with a Zoom engineer directly for confirmation, please make this possible as this is an urgent matter.

2

@elisa.zoom @TimZoom @joan.zoom Is there an email I can contact directly to a Zoom Engineer to discuss and solve this quickly?

Thanks.

3

Hello @marcok05k
Thanks for reaching out to us! We do have a lot of information about about this change, you can find it all here:

We are also providing weekly office hours where some of my colleagues can provide you with support, please register here:

I am looping in my colleagues @joan.zoom and @JenBrissman to shed some more light here!

4

Thanks, Elisa ,

We do need a bit of urgent support as we are somewhat likely affected and our situation is rather unique, (needed for user managed app approval) but I do have a few questions.

Is there any way to move an approved General / User Managed app to another Zoom account?

Thanks.

5

Hi @marcok05k
Yes, you can transfer your app to another Zoom account and our support team will be able to help you do that

Feel free to post your other questions here in this thread so we can chime in and try to resolve them!

6

Hi @elisa.zoom

OK, so that means that when we transfer our General / User Managed app to to another Zoom account the other Zoom account receiving the app can continue as normal without using OBF tokens?

Also do you have a support email or someone I can contact directly on this to transfer the Zoom account? @elisa.zoom

Thanks.

7

Hi @marcok05k -

To clarify, if the app you are transferring already has attribution implemented (for example, through an OBF Token, ZAK Token, or RTMS depending on your use case), the receiving Zoom account can continue functioning as normal after the transfer.

If the app does not currently include attribution, transferring it will not remove the need to implement it. Attribution requirements still apply for the receiving account.

For assistance with transferring your app between accounts, the link Elisa shared above is the best way to get in touch with Zoom Support. They handle all app transfer requests and can guide you through the process specific to your app type and scenario.

Let us know if you have any other questions!

8

@JenBrissman @elisa.zoom I have tried contacting Zoom Support and they pointed me to another Zoom Team which told me that I needed to contact sales to pay for a developer support plan which starts at $650/mo to move an app to another Zoom account?

I’m confused with this, as we were told that Zoom Support can deal with this and now we have to pay for a developer support plan just to move an app?

Keep in mind our app is already approved and we’d like to not go through that lengthy process again.

This is the reason I need to get in touch with a Zoom employee / engineer quickly just to move it over to another account.

I am not asking for developer code support or anything.

Thanks.

9

Hey @marcok05k
I am really sorry about that. You should not need a Premier Developer Support plan to do this.
I will personally send you a DM to collect more information and will escalate this internally

10

Hi @elisa.zoom @JenBrissman ,

We have a similar use case and currently exploring other alternatives as well. We would really appreciate some guidance as we also need to handle this urgently. Thanks!

Below are the options we are currently considering:
————————————————————————————————————
1. ISV-based approaches

Under an ISV partnership, we would like to understand whether the following models are supported:

a. Sub-accounts / internal meeting classification

  • Can external users who host meetings be onboarded as sub-accounts or customers under our main ISV account?

  • If so, would meetings hosted under these sub-accounts be considered “internal,” allowing SDK clients to join using JWT only (without ZAK or OBF)?

  • Would a single SDK app under the top-level ISV account be sufficient, or would each sub-account/customer require its own SDK app?

b. SDK app ownership / installation

  • Is it supported to programmatically create Marketplace SDK apps for external users and use their SDK keys to join meetings without OAuth?

  • If external hosts install our SDK app from the Marketplace, or are added as collaborators to our SDK app, would meetings hosted in their accounts be considered internal and allow SDK joins using JWT only?

  • Is this method only supported in ISV?

c. Managed users (custcreate)

  • If we create and manage users via the custcreate operation:

    • Can OAuth be performed programmatically on behalf of these users?

    • Can these managed users host or join meetings in external accounts while satisfying the attribution requirement?

d. ISV pricing

  • Can you share high-level ISV pricing guidance for the models above?

2. OBF token usage

  • Can a single internally controlled user obtain an OBF token that is reused across multiple SDK instances?

3. RTMS as an alternative

  • Does RTMS support gallery view?

  • Are there any public resources or high-level pricing guidance available for RTMS? We are looking at 5000 meeting hours per month at our peak usage across multiple customers.

Based on previous forum discussions, it appears there is currently no way to fully test or simulate behavior once the new requirement is enforced. Given this limitation, and the fact that we are actively engaging with Zoom Sales and the ISV team (with vendor procurement typically taking time), we would like to ask whether a temporary extension is possible to allow sufficient time to implement the correct solution.