{"version":"2.1.283","anchor":"gateway-refuses-forward-user-identity-for-claudegoogleapis","canonical_anchor":"gateway-refuses-forward-user-identity-for-claudegoogleapis","heading":"Gateway config also refuses user identity forwarding to claude.googleapis.com","tier":"notice","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/gateway-refuses-forward-user-identity-for-claudegoogleapis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Gateway config also refuses user identity forwarding to claude.googleapis.com\n\nGateway config validation now rejects `forward_user_identity` when an Anthropic upstream points at claude.googleapis.com\n\n**What**\n\nThe check that refuses the `forward_user_identity` option on Anthropic upstreams now covers one more host. A gateway config now fails validation, the check Claude Code runs on the config before using it, when the upstream's `base_url` host is `claude.googleapis.com`.\n\nThe refused hosts are now:\n\n- `anthropic.com` and any subdomain of it\n\n- the AWS external-Anthropic endpoints\n\n- `claude.googleapis.com`, which is the addition\n\n**Why**\n\nIf your gateway config sets `forward_user_identity` on an upstream pointing at `claude.googleapis.com`, that config will stop passing validation. The refusal keeps user emails from being sent to Anthropic. Remove the option from that upstream to fix it.\n\n- Area: Gateway\n- Names: `forward_user_identity`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}