Fix 403 authentication errors for UK users by adding GB country code normalization #181
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…normalization Co-authored-by: donavanbecker <[email protected]>
Copilot finished work on behalf of
donavanbecker
September 13, 2025 16:33
donavanbecker
approved these changes
Sep 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the 403 authentication errors that UK users have been experiencing since the August/Yale split when using country code 'GB'.
Problem
UK users were encountering 403 errors during authentication because the August API infrastructure doesn't have dedicated endpoints for the UK region. The plugin already had country code normalization for Canada (
CA → US) and Mexico (MX → US), but was missing the same handling for the United Kingdom.Solution
Added
'GB': 'US'to the country code normalization mapping inplatform.ts. This ensures UK users authenticate through the US endpoints, which resolves the 403 errors while maintaining all existing functionality.Changes
countryCodeMappingobject to route UK authentication through US serversgb→US)disableCountryCodeNormalizationoption for GBBackward Compatibility
This change is fully backward compatible. UK users who want to disable normalization can still use the existing
disableCountryCodeNormalization: trueoption in their configuration.Fixes #180.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.