starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Azure Cloud Shell Connector Not Working #3024

New Issue
Closed
opened 2026-01-30 23:11:04 +00:00 by claunia · 4 comments
claunia commented 2026-01-30 23:11:04 +00:00
Owner
Copy Link

Originally created by @isaacrlevin on GitHub (Jul 31, 2019).

Environment

Windows build number: 10.0.18941.1001
Windows Terminal version (if applicable): Source

Steps to reproduce

  • Fresh Install of Terminal from Source
  • Try to open Azure Cloud Shell Connector

Expected behavior

  • Device Flow kicks off and you can connect to Azure

Actual behavior

  • Get following message

Could not connect to Azure. You may not have internet or the server might be down.

Opening up Fiddler, the request is failing, here is the request

POST https://login.microsoftonline.com/common/oauth2/devicecode HTTP/1.1
Connection: Keep-Alive
Content-Type: application/x-www-form-urlencoded; charset=utf-8
User-Agent: cpprestsdk/2.10.13
Content-Length: 57
Host: login.microsoftonline.com

client_id=0&resource=https://management.core.windows.net/

and response

HTTP/1.1 400 Bad Request
Cache-Control: no-cache, no-store
Pragma: no-cache
Content-Type: application/json; charset=utf-8
Expires: -1
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
x-ms-request-id: 036d9b04-0b15-4948-88e3-1298fe521f00
P3P: CP="DSP CUR OTPi IND OTRi ONL FIN"
Set-Cookie: fpc=AgBw0kjQZyJGh-9yya_oOWo; expires=Fri, 30-Aug-2019 13:29:10 GMT; path=/; secure; HttpOnly
Set-Cookie: esctx=AQABAAAAAAAP0wLlqdLVToOpA4kwzSnx6Nn0i9n3KONl8oqKUDrwVI49N60kNuXitGhI2l65usEtATWKSOh8_SSS6SxU8qs6Mc2TKjto45yvCwsR1FnOxysOiKELlbMM8oFUyR0pRNEedN5J_pDsAlMLiz5CCixbFrYu1kevQ7G277G0tWGQ1Bmr6yQvertj7I1EFoMdyWkgAA; domain=.login.microsoftonline.com; path=/; secure; HttpOnly
Set-Cookie: x-ms-gateway-slice=prod; path=/; secure; HttpOnly
Set-Cookie: stsservicecookie=ests; path=/; secure; HttpOnly
Date: Wed, 31 Jul 2019 13:29:10 GMT
Content-Length: 468

{"error":"invalid_request","error_description":"AADSTS50059: No tenant-identifying information found in either the request or implied by any provided credentials.\r\nTrace ID: 036d9b04-0b15-4948-88e3-1298fe521f00\r\nCorrelation ID: 62f6beea-e136-430d-8262-d762ad319f00\r\nTimestamp: 2019-07-31 13:29:10Z","error_codes":[50059],"timestamp":"2019-07-31 13:29:10Z","trace_id":"036d9b04-0b15-4948-88e3-1298fe521f00","correlation_id":"62f6beea-e136-430d-8262-d762ad319f00"}

Looks like no client_ id is being set in code. Do you need to set this somewhere?

Originally created by @isaacrlevin on GitHub (Jul 31, 2019). # Environment ```none Windows build number: 10.0.18941.1001 Windows Terminal version (if applicable): Source ``` # Steps to reproduce - Fresh Install of Terminal from Source - Try to open Azure Cloud Shell Connector # Expected behavior - Device Flow kicks off and you can connect to Azure # Actual behavior - Get following message > Could not connect to Azure. You may not have internet or the server might be down. Opening up Fiddler, the request is failing, here is the request ``` POST https://login.microsoftonline.com/common/oauth2/devicecode HTTP/1.1 Connection: Keep-Alive Content-Type: application/x-www-form-urlencoded; charset=utf-8 User-Agent: cpprestsdk/2.10.13 Content-Length: 57 Host: login.microsoftonline.com client_id=0&resource=https://management.core.windows.net/ ``` and response ``` HTTP/1.1 400 Bad Request Cache-Control: no-cache, no-store Pragma: no-cache Content-Type: application/json; charset=utf-8 Expires: -1 Strict-Transport-Security: max-age=31536000; includeSubDomains X-Content-Type-Options: nosniff x-ms-request-id: 036d9b04-0b15-4948-88e3-1298fe521f00 P3P: CP="DSP CUR OTPi IND OTRi ONL FIN" Set-Cookie: fpc=AgBw0kjQZyJGh-9yya_oOWo; expires=Fri, 30-Aug-2019 13:29:10 GMT; path=/; secure; HttpOnly Set-Cookie: esctx=AQABAAAAAAAP0wLlqdLVToOpA4kwzSnx6Nn0i9n3KONl8oqKUDrwVI49N60kNuXitGhI2l65usEtATWKSOh8_SSS6SxU8qs6Mc2TKjto45yvCwsR1FnOxysOiKELlbMM8oFUyR0pRNEedN5J_pDsAlMLiz5CCixbFrYu1kevQ7G277G0tWGQ1Bmr6yQvertj7I1EFoMdyWkgAA; domain=.login.microsoftonline.com; path=/; secure; HttpOnly Set-Cookie: x-ms-gateway-slice=prod; path=/; secure; HttpOnly Set-Cookie: stsservicecookie=ests; path=/; secure; HttpOnly Date: Wed, 31 Jul 2019 13:29:10 GMT Content-Length: 468 {"error":"invalid_request","error_description":"AADSTS50059: No tenant-identifying information found in either the request or implied by any provided credentials.\r\nTrace ID: 036d9b04-0b15-4948-88e3-1298fe521f00\r\nCorrelation ID: 62f6beea-e136-430d-8262-d762ad319f00\r\nTimestamp: 2019-07-31 13:29:10Z","error_codes":[50059],"timestamp":"2019-07-31 13:29:10Z","trace_id":"036d9b04-0b15-4948-88e3-1298fe521f00","correlation_id":"62f6beea-e136-430d-8262-d762ad319f00"} ``` Looks like no client_ id is being set in code. Do you need to set this somewhere?
claunia commented 2026-01-30 23:11:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 31, 2019):

This definitely isn't supposed to work at the moment. We need to manually embed our client ID in the code, and we're definitely not pushing that to the repo. We'll stamp that client ID into the build during the release process, but it won't work in local builds unfortunately.

This is now the issue for "Display a message when someone tries to use the azure connection in a local build without the client ID".

CC @PankajBhojwani and @DHowett-MSFT

@zadjii-msft commented on GitHub (Jul 31, 2019): This definitely isn't supposed to work at the moment. We need to manually embed our client ID in the code, and we're definitely not pushing that to the repo. We'll stamp that client ID into the build during the release process, but it won't work in local builds unfortunately. This is now the issue for "Display a message when someone tries to use the azure connection in a local build without the client ID". CC @PankajBhojwani and @DHowett-MSFT
claunia commented 2026-01-30 23:11:06 +00:00
Author
Owner
Copy Link

@isaacrlevin commented on GitHub (Jul 31, 2019):

So is there a workaround at the moment? Or should we just remove the profile?

@isaacrlevin commented on GitHub (Jul 31, 2019): So is there a workaround at the moment? Or should we just remove the profile?
claunia commented 2026-01-30 23:11:06 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Aug 1, 2019):

There is no workaround right now, you can remove the profile if you don't want it. We will make it so this option does not show up in local builds in the future. Thank you!

@PankajBhojwani commented on GitHub (Aug 1, 2019): There is no workaround right now, you can remove the profile if you don't want it. We will make it so this option does not show up in local builds in the future. Thank you!
claunia commented 2026-01-30 23:11:06 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 27, 2019):

:tada:This issue was addressed in #2195, which has now been successfully released as Windows Terminal Preview v0.4.2382.0.🎉

Handy links:

@ghost commented on GitHub (Aug 27, 2019): :tada:This issue was addressed in #2195, which has now been successfully released as `Windows Terminal Preview v0.4.2382.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v0.4.2382.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-UserInterface Issue-Task Needs-Tag-Fix Product-Terminal Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#3024
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?