{"version":"2.1.280","anchor":"gateway-provider-type-now-correctly-maps-to-thirdparty","canonical_anchor":"gateway-provider-type-now-correctly-maps-to-thirdparty","heading":"'gateway' provider type now correctly maps to thirdParty","tier":"internal","area":"Auth","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/gateway-provider-type-now-correctly-maps-to-thirdparty","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### 'gateway' provider type now correctly maps to thirdParty\n\nThe 'gateway' provider\/auth type is now correctly classified as thirdParty instead of being unclassified\n\n**What**\n\nInternal logic that classifies which kind of provider or authentication setup is in use previously had a gap: the 'gateway' case fell through without being classified, returning nothing. It now correctly groups with foundry, anthropicAws, and anthropicGoogleCloud under the 'thirdParty' category.\n\n**Why**\n\nAny code that branches on this classification (such as feature gating or provider-specific behavior) now handles gateway setups consistently with other third-party providers instead of silently falling through unclassified.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}