Public Client PKCE OAuth — Invalid Redirect URL with Dynamic Loopback Port

API Endpoint(s)

https://zoom.us/oauth/authorize

Description

I’m developing a Windows desktop application that uses Zoom OAuth with a Public Client ID and PKCE S256 to retrieve authorized Zoom Team Chat messages.

Zoom rejects the authorization request with an “Invalid redirect URL” error, even though the application configuration appears to follow Zoom’s documentation.

Application configuration:

  • App type: General App

  • Management: User-managed

  • Environment: Development

  • Public Client OAuth: Enabled

  • Authentication: Authorization Code with PKCE S256

  • Registered PKCE OAuth Redirect URL: http://127.0.0.1/callback

  • OAuth Allow List includes: http://127.0.0.1/callback

  • Client ID: Public Client ID (not the regular OAuth Client ID)

The desktop application starts a local HTTP listener using an available temporary port.

For example, it generated:

http://127.0.0.1:59679/callback

My understanding is that Zoom supports dynamically assigned loopback ports for PKCE public clients and ignores the port when matching the registered redirect URI.

Error

Zoom displays:

“You cannot authorize [application name] — Invalid redirect URL.”

The rejection occurs before Zoom redirects to the local application.

How to Reproduce

  1. Create a user-managed General App in Zoom Marketplace’s Development environment.

  2. Enable Public Client OAuth.

  3. Register http://127.0.0.1/callback as the PKCE OAuth Redirect URL.

  4. Include that address in the OAuth Allow List.

  5. Initiate authorization using the Public Client ID, authorization code flow, and PKCE S256.

  6. Supply a redirect URI using the same host and path with a dynamically assigned port, such as http://127.0.0.1:59679/callback.

  7. Zoom rejects the request with “Invalid redirect URL.”

Questions

  1. Does Zoom currently support dynamic loopback ports for PKCE public clients using user-managed General Apps in Development mode?

  2. Is additional application configuration required?

  3. Should the callback URL also be registered somewhere other than the PKCE OAuth Redirect URL and OAuth Allow List fields?

  4. Is this a known redirect-validation issue?

  5. Is there another recommended authorization approach for a local Windows desktop application that does not require embedding a Client Secret?

Any guidance would be appreciated.

Thank you.