While we normally recommend DeviceCodeAuthentication for scenarios where the default browser cannot be opened, we could provide additional flexibility in IBC to support GH Codespaces. One solution was provided by a contributor in #28968 which we ultimately decided not to bring into the public surface area.

However, we could think through alternatives and/or revisit that decision. This issue tracks work to support IBC in GH Codespaces

Acceptance Criteria:

• I can use IBC in a codespace with some additional configuration
• Threat modeling is performed for the scenario

A lighter solution that was proposed was to allow the user to specify the port in advance. Alternatively, overriding the openBrowser flow may be more flexible.