{"version":"2.1.228","anchor":"gateway-config-now-rejects-unsafe-customer-routed-inference-","canonical_anchor":"gateway-config-now-rejects-unsafe-customer-routed-inference-","heading":"Gateway config now rejects unsafe customer-routed-inference setups","tier":"notice","area":"Gateway","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/gateway-config-now-rejects-unsafe-customer-routed-inference-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Gateway config now rejects unsafe customer-routed-inference setups\n\nGateway config refuses to start with an empty audience or organization allowlist.\n\n**What**\n\nOperator config parsing fails a deployment that enables customer-routed inference with an empty audience list or an empty organization allowlist. `oidc` is now required unless customer-routed inference is enabled.\n\n**Details**\n\n- The rejection messages spell out the reason: audience binding is what stops a token minted for another organization's gateway from being replayed against yours.\n\n**Evidence**\n\n`oidc is required \\u2014 it may be omitted only for a customer-routed-inference-only deployment (cri.enabled: true)`\n\n- Area: Gateway\n- Names: `oidc`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}