Right,
But that’s the problem: the CA user who happens to be connecting the same Zoom account has no formal connection to the other CA user who authorized it the first time.
Again, two separate CA users, connecting to the same Zoom account.
In our example, betty@acmecoaches.com within CA is a fully separate entity from betty@bettyscoaching.com.
CA has no reason to know or to be able to recognize those are using the same Zoom account. Therefore CA cannot decide that when betty@bettyscoaching.com connects a Zoom account that it should use that new token for the bett@acmecoaches.com account.
As such, the token from the 2nd authorization cannot be used on behalf of both Betty’s CA accounts.
The root problem is that Zoom seems to assume that connecting a second time indicates a user’s desire to disconnect the first. That assumption is flawed, and causes problems contrary to the user’s wishes.