{"version":"2.1.224","anchor":"sandbox-proxy-credentials-are-unique-per-sandbox-instance","canonical_anchor":"sandbox-proxy-credentials-are-unique-per-sandbox-instance","heading":"Sandbox proxy credentials are unique per sandbox instance","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/sandbox-proxy-credentials-are-unique-per-sandbox-instance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Sandbox proxy credentials are unique per sandbox instance\n\nConcurrent sandboxes now get unique proxy usernames instead of sharing one identity.\n\n**What**\n\nProxy settings injected into the sandbox (`HTTP_PROXY`, `ALL_PROXY`, `CLOUDSDK_PROXY_USERNAME`, and the socat\/ssh ProxyCommand) now use a username with an instance suffix rather than the fixed `srt`, so concurrent sandboxes no longer share one identity. If the suffixed name would exceed 255 bytes it falls back to plain `srt`.\n\n**Evidence**\n\n`CLOUDSDK_PROXY_USERNAME=`\n\n- Area: Sandbox\n- Names: `HTTP_PROXY`, `ALL_PROXY`, `CLOUDSDK_PROXY_USERNAME`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}