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

400 Client Error in Azure Cloud Shell Connector #3324

New Issue
Open
opened 2026-01-30 23:18:36 +00:00 by claunia · 5 comments
claunia commented 2026-01-30 23:18:36 +00:00
Owner
Copy Link

Originally created by @TechWatching on GitHub (Aug 9, 2019).

Originally assigned to: @DHowett on GitHub.

Environment

Windows build number: Microsoft Windows [version 10.0.18362.10005]
Windows Terminal version (if applicable): 0.3.2171.0

Steps to reproduce

1- Open a new CloudShell tab and log in
2- Execute some azure cli commands for about 10 min

Expected behavior

Azure CLI commands continue to execute without any problem

Actual behavior

After some time, the azure cli commands will failed with the following error :
Error occurred in request., HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token

Executig several times the same commands (az keyvault secret show --vault-name $kvName -n $secretName --query id -o tsvfor instance) won't change anything. However the azure cloud shell is opened in the browser (shell.azure.com) the same command will work and executing azure cli commands will start working again in the azure cloud shell of windows terminal.

Originally created by @TechWatching on GitHub (Aug 9, 2019). Originally assigned to: @DHowett on GitHub. # Environment Windows build number: Microsoft Windows [version 10.0.18362.10005] Windows Terminal version (if applicable): 0.3.2171.0 # Steps to reproduce 1- Open a new CloudShell tab and log in 2- Execute some azure cli commands for about 10 min # Expected behavior Azure CLI commands continue to execute without any problem # Actual behavior After some time, the azure cli commands will failed with the following error : ```Error occurred in request., HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token``` Executig several times the same commands (```az keyvault secret show --vault-name $kvName -n $secretName --query id -o tsv```for instance) won't change anything. However the azure cloud shell is opened in the browser (shell.azure.com) the same command will work and executing azure cli commands will start working again in the azure cloud shell of windows terminal.
claunia added the Help WantedIssue-BugProduct-TerminalArea-AzureShell labels 2026-01-30 23:18:37 +00:00
claunia commented 2026-01-30 23:18:37 +00:00
Author
Owner
Copy Link

@TechWatching commented on GitHub (Aug 12, 2019):

This error always appears when doing a command linked to azure AD like az ad user list . It works fine on shell.azure.com but not in WindowsTerminal.

@TechWatching commented on GitHub (Aug 12, 2019): This error always appears when doing a command linked to azure AD like `az ad user list` . It works fine on shell.azure.com but not in WindowsTerminal.
claunia commented 2026-01-30 23:18:38 +00:00
Author
Owner
Copy Link

@GillesZunino commented on GitHub (Dec 24, 2019):

Giving this a +1 - Adding / retrieving secrets is a common operation when running deploying scripts and this issue makes it near impossible to use Cloud Shell Connector for anything serious.

  • Using Terminal 0.7.3451.0 - Open a Cloud Shell Connector and connect to an active Azure subscription
  • Make sure the subscription has a vault called "SecureSecretVault" and it contains a secret called "TheSecret"
  • Run the following: az keyvault secret show --name "TheSecret" --vault-name "SecureSecretVault"

OBSERVE:
Error occurred in request., HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token

EXPECTED:
The secret value is displayed

@GillesZunino commented on GitHub (Dec 24, 2019): Giving this a +1 - Adding / retrieving secrets is a common operation when running deploying scripts and this issue makes it near impossible to use Cloud Shell Connector for anything serious. - Using Terminal 0.7.3451.0 - Open a Cloud Shell Connector and connect to an active Azure subscription - Make sure the subscription has a vault called "SecureSecretVault" and it contains a secret called "TheSecret" - Run the following: `az keyvault secret show --name "TheSecret" --vault-name "SecureSecretVault"` OBSERVE: `Error occurred in request., HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token` EXPECTED: The secret value is displayed
claunia commented 2026-01-30 23:18:38 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 11, 2020):

Alright, finally figured this one out. It's a chunk of work to support it, but it looks like AZCs has a "control" channel that it can use to request additional authentication/do other exchanges with the thing that's hosting it (typically the cloud shell javascript.)
One of those requests is for "token". 😄

@DHowett-MSFT commented on GitHub (Feb 11, 2020): Alright, finally figured this one out. It's a chunk of work to support it, but it looks like AZCs has a "control" channel that it can use to request additional authentication/do other exchanges with the thing that's hosting it (typically the cloud shell javascript.) One of those requests is for "token". :smile:
claunia commented 2026-01-30 23:18:38 +00:00
Author
Owner
Copy Link

@bandwiches commented on GitHub (Jun 24, 2020):

Do you propose any workarounds for #6038 besides the browser shell in the Azure Portal (which isn't really viable)? I'm unable to do anything remote since the session cannot be loaded. Thanks!

@bandwiches commented on GitHub (Jun 24, 2020): Do you propose any workarounds for [#6038](https://github.com/microsoft/terminal/issues/6038) besides the browser shell in the Azure Portal (which isn't really viable)? I'm unable to do anything remote since the session cannot be loaded. Thanks!
claunia commented 2026-01-30 23:18:38 +00:00
Author
Owner
Copy Link

@wasker commented on GitHub (Oct 21, 2020):

Hi,

Are there any plans to address this issue? Is there a documentation on the "control channel" one could use to contribute the fix?

@wasker commented on GitHub (Oct 21, 2020): Hi, Are there any plans to address this issue? Is there a documentation on the "control channel" one could use to contribute the fix?
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-AzureShell Help Wanted Issue-Bug Product-Terminal
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#3324
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?