{"version":"2.1.296","anchor":"gateway-login-method-now-counts-as-gateway-required","canonical_anchor":"gateway-login-method-now-counts-as-gateway-required","heading":"Setting forceLoginMethod to gateway now leads to the gateway login","tier":"use","area":"Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/gateway-login-method-now-counts-as-gateway-required","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Setting forceLoginMethod to gateway now leads to the gateway login\n\nWith forceLoginMethod set to \"gateway\" and no forceLoginGatewayUrl, Claude Code now treats gateway login as required\n\n**What**\n\nClaude Code now treats logging in through a gateway as required when `forceLoginMethod` is set to `\"gateway\"` and `forceLoginGatewayUrl` is not set. A gateway is a server your organization runs that you log in through. Before, only a condition tied to `policyHelper`, a setting that runs a program to compute managed settings, led to this.\n\n**Why**\n\nIf your managed settings (the ones an administrator controls) set `forceLoginMethod` to `\"gateway\"` without giving a gateway address, you now get the gateway login flow.\n\n- Area: Gateway\n- Names: `forceLoginMethod`, `forceLoginGatewayUrl`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}