{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiff7vxxu4lzv5y47fidsnfa4wodsoxmpqtczaslvusamz5e5q2j7m",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mfmm7pzvzkk2"
  },
  "path": "/t/missing-openid-scope-in-dynamically-registered-oauth-clients/1368690#post_5",
  "publishedAt": "2026-02-24T15:26:39.000Z",
  "site": "https://community.openai.com",
  "tags": [
    "Developer Mode & MCP Apps",
    "@mikkokutilainen"
  ],
  "textContent": "Hey @mikkokutilainen @Mohamed_Mamdouh, yeah, that’s a confusing one.\n\nWhen using DCR, ChatGPT handles the OAuth client creation automatically, but it still depends on the provider correctly supporting standard OAuth/OIDC behavior, as outlined in the Developer Mode & MCP Apps guide. If a required scope isn’t included at registration time but is later requested during auth, the flow can fail.\n\nQuick checks that would help:\n\n  * Is openid present in the DCR request and Clerk is dropping it?\n  * Or is it missing already in the registration payload?\n  * Rough timestamp with timezone of a failed attempt?\n\n\n\nIf this happens consistently with a fresh app and fresh DCR, that’s useful signal. Let’s narrow down whether this is Clerk specific or something broader.",
  "title": "Missing 'openid' scope in dynamically registered OAuth clients"
}