# Public PKCE second authorization invalidates previous independent user grant

**URL:** <https://devforum.zoom.us/t/public-pkce-second-authorization-invalidates-previous-independent-user-grant/147281>\
**Category:** Authentication\
**Created:** [October 20, 2026, 7:24am UTC](https://devforum.zoom.us/t/public-pkce-second-authorization-invalidates-previous-independent-user-grant/147281 "2026-10-20T07:24:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![PragmaticHQDev](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/pragmatichqdev/32/77414_2.png) [@PragmaticHQDev](https://devforum.zoom.us/u/PragmaticHQDev)\
**Post date:** [October 20, 2026, 7:24am UTC](https://devforum.zoom.us/t/public-pkce-second-authorization-invalidates-previous-independent-user-grant/147281/1 "2026-10-20T07:24:59Z")

</div>

We need one staff user to authorize the same Zoom identity independently in two company workspaces. We never copy tokens between companies.

Reproduction:

1. Enable the app’s separate public PKCE client. Use its public client ID (not the confidential ID), S256, a fresh verifier and company/person-bound state. We verified the actual authorization request uses the separate public client ID.
2. Authorize the same owned test Zoom identity for companyA. Exchange its authorization code without a client secret, save the returned access/refresh tokens privately, and call GET /v2/users/me successfully.
3. Independently authorize the same Zoom identity for companyB using a fresh public-PKCE authorization flow. Its code exchange and GET /v2/users/me succeed.
4. Calling GET /v2/users/me with the older companyA access token now returns HTTP401. Refreshing the older grant fails. Refreshing the newest grant succeeds, but does not make the older grant usable.
5. Reauthorize companyA: A works again while B’s older grant returns HTTP401. The behavior repeats.

Scopes: user:read:user, meeting:write:meeting, meeting:delete:meeting, meeting:read:list\_meetings, meeting:read:meeting.

We reproduced this with an HTTPS callback and an allowed numeric-loopback callback. Normal single-company OAuth and real booking/create/busy/reschedule/cancel meeting lifecycle work. Our refresh tokens have a single-consumer lease; unknown outcomes stop and require reconnect, rather than being replayed.

Your OAuth documentation says enabling a public client automatically enables multi-auth token mode and allows previously issued valid user tokens to keep working:

> **[Supporting concurrent logins - OAuth 2.0 - Integrations - Zoom Developer Docs](https://developers.zoom.us/docs/integrations/oauth/#supporting-concurrent-logins)**
>
> OAuth 2.0 lets your app securely access Zoom APIs for users or accounts. Zoom supports industry-standard OAuth 2.0 (rfc6749 ) flows to handle authorization and access tokens. | Learn how to request, refresh, and revoke OAuth 2.0 access tokens for...

Is there an additional setting or request parameter needed to enable multi-auth token mode for a General app with public PKCE? Are there Development environment restrictions? We need a supported approach for independent simultaneous authorizations without sharing credentials between companies. We can provide app-specific details privately to Zoom staff if needed.

No passwords, client IDs/secrets, authorization codes, access/refresh tokens, customer records or meeting links are included in this post.
