Unable to use SOCKS proxy with Entra ID / OIDC authentication: missing 'socks' dependency for MongoDB connection

[ahmedyoussef-au]

Bug Description

The extension cannot connect to MongoDB databases over a SOCKS proxy because the required socks package is not included in the extension bundle. This breaks support for the proxyHost connection option, which is documented as supported in the upstream MongoDB Node.js driver (mongodb@~7.0.0).

Steps to Reproduce

1. Attempt to connect to a MongoDB/CosmosDB database using Entra ID authentication (with authMechanism=MONGODB-OIDC) and supplying a proxyHost=... and proxyPort=... option in the connection string (for example, behind a SOCKS5 jumpbox/proxy server).
2. The connection attempt times out after ~30 seconds and fails internally with kModuleError from getSocks()
3. No user-facing error indicates that the socks package is missing

Expected Behavior

• Extension should include the socks package in its dependencies and bundle it correctly
• When proxyHost/proxyPort are specified, the extension should route the connection through a SOCKS5 proxy as supported by the upstream driver

Actual Behavior

• The extension fails to establish a connection over a SOCKS proxy
• Ultimately leads to timeout and internal error, sometimes with an unhelpful error message
• Debug logs reveal kModuleError when trying to require socks

Environment

• Extension version: 0.7.2
• Node.js MongoDB driver bundled: ~7.0.0
• Host OS: [Please fill in]

Additional Context

• Upstream driver: https://github.com/mongodb/node-mongodb-native/blob/v7.0.0/src/cmap/connect.ts#L269
• The socks package is required but not present in the VS Code extension's package.json dependencies or the extension bundle
• This blocks users who can only reach the database via a SOCKS5 proxy (e.g., jump host, cloud bastion) and need to use the OIDC/Entra ID authentication mechanism

Request:

• Please add socks as a dependency and bundle it to restore support for connecting via a SOCKS proxy with Entra ID (OIDC) authentication.

Thank you!

[tnaum-ms]

@ahmedyoussef-au Thank you for reporting this issue. I'm scheduling a detailed review of this issue for the 0.8.1 milestone (approx. 2wks from now). Based on the outcome we'll schedule a fix.