Switch Interactive Auth to DeviceCode in CodeSpaces and non-WSL Remote scenarios #221
Conversation
This file contains 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
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.
AB#2694410
When the user is running PAC in a remote scenario such as CodeSpaces or SSH (but not WSL remoting), we cannot use Interactive Auth, as the
localhostof the machine running PAC is not the samelocalhostas the machine running the browser.For these scenarios, the user can just use
--deviceCode. If they don't supply that arg however, they end in a state that can never return control back to the user, as PAC is waiting for redirect that will never come.This change sets an Environment Variable in those cases, which PAC uses to default in the device code flow instead of Interactive.