# Missing 'openid' scope in dynamically registered OAuth clients

**URL:** <https://community.openai.com/t/missing-openid-scope-in-dynamically-registered-oauth-clients/1368690>\
**Category:** ChatGPT Apps SDK\
**Created:** [December 8, 2025, 8:42am UTC](https://community.openai.com/t/missing-openid-scope-in-dynamically-registered-oauth-clients/1368690 "2025-12-08T08:42:23Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Evan\_Fenster](https://sea2.discourse-cdn.com/openai1/user_avatar/community.openai.com/evan_fenster/32/513141_2.png) [@Evan\_Fenster](https://community.openai.com/u/Evan_Fenster)\
**Post date:** [February 23, 2026, 8:58pm UTC](https://community.openai.com/t/missing-openid-scope-in-dynamically-registered-oauth-clients/1368690/3 "2026-02-23T20:58:12Z")

</div>

Hi @mikkokutilainen @Mohamed_Mamdouh , we encountered the same issue.

You may be able to go in and manually add `openid` after the initial registration, but this is sometimes tricky with the timing. Another solution is to manually create the client in Clerk with `openid` and the other fields included, and then add the `Oauth client ID` and `Oauth client secret` manually when creating the App in ChatGPT (screenshot attached).

Let me know if either of these work for you, or if you find a more reliable way to get `openid` working with DCR.

 ![Screenshot 2026-02-23 at 3.54.18 PM](https://us1.discourse-cdn.com/openai1/original/4X/f/4/d/f4d9a9470be279670efb35156b095387516fd40e.png)

---

_[View the full topic](https://community.openai.com/t/missing-openid-scope-in-dynamically-registered-oauth-clients/1368690)._
