{"version":"2.1.224","anchor":"sandbox-credential-matching-ignores-ports-and-schemes-in-hos","canonical_anchor":"sandbox-credential-matching-ignores-ports-and-schemes-in-hos","heading":"Sandbox credential matching ignores ports and schemes in host entries","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/sandbox-credential-matching-ignores-ports-and-schemes-in-hos","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Sandbox credential matching ignores ports and schemes in host entries\n\nSandbox credential host entries written with a port or scheme now still match.\n\n**What**\n\nHost entries controlling which credentials get injected into a sandbox are now normalized to a bare host pattern and de-duplicated before matching, so an entry written with a port or scheme still matches, and repeated entries collapse.\n\n**Details**\n\n- Applies to the environment variable, AWS key-pair and masked-file credential resolution paths.\n- Only affects the sandbox credential configuration path.\n\n**Evidence**\n\n`degradeToUnsetNames`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}