sign in failure, redirected to http://127.0.0.1:7/callback?code=

[liranms]

Issue Type: Bug

when signing in to my account, the server redirects to http://127.0.0.1:7/callback?code=AQABA....&session_state=7c58258e-f09c-4e59-9638-6d0a7a7e834e&state=59647%2CyI5sFkYvIs18JjUpZo3BGQ%3D%3D

VS Code is waiting for the response but its an endless wait

Extension version: 0.8.0
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item	Value
CPUs	Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2904)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled
Memory (System)	31.74GB (13.61GB free)
Process Argv
Screen Reader	no
VM	0%

[liranms]

This is the URL that VS Code spawns the browser with:

https://login.microsoftonline.com/common/oauth2/authorize?response_type=code&client_id=aebc6443-996d-45c2-90f0-388ff96faa56&redirect_uri=https://vscode-redirect.azurewebsites.net/&state=59743,LuDSB6UCCLFQhJZuF8AbHA==&resource=https://management.core.windows.net/&prompt=select_account

[chrmarti]

@liranms I'm surprised it uses port 7 in your first URI, does it always end there? The second URI shows it should end up at port 59743, does it do that?

[liranms]

Yes it's always 7
If I manually change the the port in the failed URL to the one mentioned on "state" variable, it completes the handshake

[chrmarti]

Which browser are you using? Could you check in its developer tools what the redirect header looks like that redirects to 127.0.0.1?

[vscodebot]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[sdjnaik]

Hi,

Any updates on above mentioned issue? I am also facing same issue during sign in.

[chrmarti]

@sdjnaik Could you open a new issue for us to investigate? Thanks.

[sdjnaik]

I am able to get it work through Azure App Services. No-longer facing this issue

[voltes-7777]

had the same issue and issue was fixed after setting "http:proxy support" in settings to off.