{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicfzavd2j2f7h4ycbam5mxy44m3ooo7ge7xesblrmilxpcgjj6cga",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mfkprwemibs2"
  },
  "path": "/t/missing-openid-scope-in-dynamically-registered-oauth-clients/1368690#post_3",
  "publishedAt": "2026-02-23T20:58:12.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "@mikkokutilainen",
    "@Mohamed_Mamdouh"
  ],
  "textContent": "Hi @mikkokutilainen @Mohamed_Mamdouh , we encountered the same issue.\n\nYou 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).\n\nLet me know if either of these work for you, or if you find a more reliable way to get `openid` working with DCR.\n\n",
  "title": "Missing 'openid' scope in dynamically registered OAuth clients"
}