{"version":"2.1.227","anchor":"enterprise-oidc-login-can-route-identity-provider-requests-t","canonical_anchor":"enterprise-oidc-login-can-route-identity-provider-requests-t","heading":"Enterprise OIDC login can route identity provider requests through a proxy","tier":"use","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/enterprise-oidc-login-can-route-identity-provider-requests-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Enterprise OIDC login can route identity provider requests through a proxy\n\nEnterprise OIDC logins can route identity provider requests through your configured HTTPS proxy.\n\n**What**\n\nOIDC configuration accepts a new optional `use_proxy` boolean. Set it to `true` and requests to your identity provider go through `HTTPS_PROXY`\/`HTTP_PROXY`. Leave it out while a proxy is configured and Claude Code now warns that those requests currently go direct and will follow the proxy by default in a future release, pointing you at `oidc.use_proxy: true` to adopt the new behaviour now or `false` to silence the warning.\n\n**Details**\n\n- Setting the key to true with no usable proxy variable also warns, and requests still go direct.\n- Only reachable on installs that use OIDC identity provider login.\n\n**Evidence**\n\n`oidc.use_proxy is set but no usable HTTPS_PROXY\/HTTP_PROXY is set; IdP requests go direct`\n\n- Area: Auth\n- Names: `oidc.use_proxy`, `HTTPS_PROXY`, `HTTP_PROXY`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}