{"version":"2.1.228","anchor":"gateway-runs-without-an-oidc-block-and-names-two-more-upstre","canonical_anchor":"gateway-runs-without-an-oidc-block-and-names-two-more-upstre","heading":"Gateway runs without an OIDC block, and names two more upstream failures","tier":"use","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/gateway-runs-without-an-oidc-block-and-names-two-more-upstre","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Gateway runs without an OIDC block, and names two more upstream failures\n\nYou can run claude gateway without any OIDC config; sign-in endpoints simply return 404.\n\n**What**\n\n`claude gateway` no longer requires OIDC configuration. With it absent, the device authorization endpoints return 404 \"not found\", discovery advertises no supported grant types, and the Google groups warning is suppressed. Upstream errors 413 and 501 now get readable messages.\n\n**Details**\n\n- Affected endpoints: `GET \/device`, `POST \/device`, and `\/oauth\/device_authorization`.\n- Discovery reports `grant_types_supported: []` when OIDC is not configured.\n- 413 reads \"request too large for this upstream\"; 501 reads \"upstream does not support this endpoint\".\n\n**Evidence**\n\n`upstream does not support this endpoint`\n\n- Area: Gateway\n- Names: `claude gateway`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}