# Unable to create OAuth app with custom scheme for PKCE

**URL:** <https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569>\
**Category:** App Marketplace\
**Tags:** oauth, pkce\
**Created:** [February 19, 2022, 5:46pm UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569 "2022-02-19T17:46:13Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonskeet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonskeet/32/8028_2.png) [@jonskeet](https://devforum.zoom.us/u/jonskeet)\
**Post date:** [February 19, 2022, 5:46pm UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/1 "2022-02-19T17:46:13Z")

</div>

**Description**  
I’m trying to follow the OAuth PKCE guide at [https://marketplace.zoom.us/docs/sdk/native-sdks/auth/support-oauth-SDK-app](https://marketplace.zoom.us/docs/sdk/native-sdks/auth/support-oauth-SDK-app)

It states:

> 1. In your OAuth application on Marketplace, put the custom URL scheme in the redirect URL and allow list.

So I tried that, using `myapp://myapp.zoom.us?code` for both the redirect URL and in the OAuth Allow List section. In both places, there’s a red error message of “Wrong URL format”. See the screenshot below for an example. (I’ve tried it with various other custom schemes. Only http and https appear to be allowed. Although even there, a path-and-query of `myapp.zoom.us?code` fails validation for some reason. `myapp.zoom.us/?code` passes validation.)

I can see three possibilities here:

- I’m doing something wrong, and custom schemes are supported by Zoom servers and the Marketplace
- Custom URL schemes are supported by Zoom servers, but the Marketplace admin side is being overzealous on its validation
- Custom URL schemes aren’t actually supported at all

Please could you clarify which possibility is actually the case? If it’s the third, please could you change the documentation to avoid giving the impression that custom URL schemes _are_ supported?

**Screenshots (If applicable)**

 ![Error for custom URL scheme](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/e/a/ea23d7852947282bb1974a6df1aa937982956814.png)

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [February 21, 2022, 11:29pm UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/2 "2022-02-21T23:29:20Z")

</div>

Hi @jonskeet ,

Ahh! I’m pretty sure client url schemes have been deprecated so let me verify this with our team and address the documentation.

Thank you,  
Gianni

---

<div class="post-metadata">

**Author:** ![jonskeet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonskeet/32/8028_2.png) [@jonskeet](https://devforum.zoom.us/u/jonskeet)\
**Post date:** [February 22, 2022, 7:17am UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/3 "2022-02-22T07:17:25Z")

</div>

That would be a pity - it did look like it was going to make things simpler.

Between out-of-date documentation as per this post, various aspects of confusion I laid out a while ago in [an earlier post](https://h-a-non-logged-in-user/61936/11), and [another post which went completely unanswered](https://devforum.zoom.us/t/oauth-apps-publishing-and-private-app-use-cases/62068/2), I’m finding it really hard to move from email/password login to OAuth ☹

---

<div class="post-metadata">

**Author:** ![jonskeet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonskeet/32/8028_2.png) [@jonskeet](https://devforum.zoom.us/u/jonskeet)\
**Post date:** [March 3, 2022, 9:54am UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/4 "2022-03-03T09:54:36Z")

</div>

Any update on this? The documentation looks like it’s still the same, and time is ticking away before the old SDKs supporting username/password login will be discontinued.

I can see that the move to OAuth is important for Zoom, but I’d really appreciate some more support in actually implementing it.

---

<div class="post-metadata">

**Author:** ![jonskeet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonskeet/32/8028_2.png) [@jonskeet](https://devforum.zoom.us/u/jonskeet)\
**Post date:** [March 24, 2022, 2:45pm UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/5 "2022-03-24T14:45:47Z")

</div>

Pinging this to avoid it being closed… @gianni.zoom any updates you could share with us?

---

<div class="post-metadata">

**Author:** ![jonskeet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonskeet/32/8028_2.png) [@jonskeet](https://devforum.zoom.us/u/jonskeet)\
**Post date:** [April 10, 2022, 4:52pm UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/6 "2022-04-10T16:52:14Z")

</div>

@jon.zoom Pinging you as you’ve been responsive in the past, and I’ve heard nothing since February. Any chance of an update here?

(The whole “migrating from email/password to OAuth” task is still rather problematic IMO, given the [unaddressed marketplace concerns](https://devforum.zoom.us/t/oauth-apps-publishing-and-private-app-use-cases/62068) and out-of-date documentation noted here. It’s not giving me much confidence.)

---

<div class="post-metadata">

**Author:** ![andrew.sosna](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/andrew.sosna/32/19365_2.png) [@andrew.sosna](https://devforum.zoom.us/u/andrew.sosna)\
**Post date:** [April 11, 2022, 5:19pm UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/7 "2022-04-11T17:19:55Z")

</div>

@jonskeet I think I had the same issue, and it looks like custom schemes are not supported in OAuth apps but are indeed supported in SDK OAuth apps, at least it worked for our test app.

---

<div class="post-metadata">

**Author:** ![jonskeet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonskeet/32/8028_2.png) [@jonskeet](https://devforum.zoom.us/u/jonskeet)\
**Post date:** [April 15, 2022, 7:47am UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/8 "2022-04-15T07:47:34Z")

</div>

Unfortunately you can only have a single SDK app, and I don’t want to convert that into an OAuth app in case that causes problems for my existing application.

(Fundamentally it feels like we really just need much better documentation for this, and for it to be accurate and up-to-date.)

---

<div class="post-metadata">

**Author:** ![jonskeet](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonskeet/32/8028_2.png) [@jonskeet](https://devforum.zoom.us/u/jonskeet)\
**Post date:** [May 12, 2022, 1:59pm UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/9 "2022-05-12T13:59:31Z")

</div>

Just to confirm, after converting my SDK app to OAuth (which _doesn’t_ seem to have caused any problems), I can indeed use the custom scheme.

It would be good if the documentation could be updated to clarify this.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [June 11, 2022, 11:59pm UTC](https://devforum.zoom.us/t/unable-to-create-oauth-app-with-custom-scheme-for-pkce/64569/10 "2022-06-11T23:59:52Z")

</div>

Closed on June 11, 2022, 11:59pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
