aws / aws/aws-toolkit-vscode

VSCode: How to login on a ssh remote connection via a proxy and sso?

Open
#8,125 2 comments 0 reactions 0 assignees View on GitHub
guidance
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

- OS: RHEL 9
- Visual Studio Code version: 1.103.2
- AWS Toolkit version:
- Amazon Q version: 1.97.0

## Question

1. I run VSCode on Windows remoting into a RHEL9 machine via SSH.
2. Everything needs a proxy to connect to internet
3. On the remote I successfully installed and used `q`: I needed `https_proxy` and `SSL_CERT_FILE`
4. The VSCode extension fails with `UNABLE_TO_VERIFY_LEAF_SIGNATURE` soon after an attempt to retrieve a `1.x.json`
5. The 2 above env vars are available in VSCode too
6. I added the same `.pem` file in the VSCode settings (Certificate Authority)

Any suggestion?

I know it is bad, but, can we just disable SSL verification altogether? In corporate environments it is a guaranteed headache.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the VS Code extension's remote-SSH login through the corporate proxy with https_proxy and SSL_CERT_FILE set, then compare it with the working q command. Check whether the VS Code Certificate Authority setting is applied to the extension's remote process. Done means the extension can retrieve its 1.x.json and complete SSO, or the supported limitation and SSL-verification policy are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, vscode
Domain
authentication, developer-experience, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.