For SqlServer I see no way to set TrustServerCertificate=True

[uptondev]

Extension Version

2.6.2

OS and Version

Windows 10

VS Code Version

v1.99.3

Database name and Version

Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64) Oct 8 2022 05:58:25 Copyright (C) 2022 Microsoft Corporation Express Edition (64-bit) on Windows 10 Pro 10.0 (Build 19045: ) (Hypervisor)

Steps to reproduce

Steps to Reproduce:

1. Launch SSMS and connect with credentials below. Verify it works.
2. Launch VS Code
3. Edit .devdbrc to look like this:
   {
   "name": "My Sql Server",
   "type": "mssql",
   "host": "DESKTOP-YODA\SQLEXPRESS",
   "port": 1433,
   "username": "someROuser",
   "password": "someROuserPwd",
   "database": "TestDatabase"
   }
4. Get a message toast that says...
   "The MSSQL connection My Sql Server specified in your config file is not valid" Source: DevDb

Expected behavior

I expected the database tools to pop up in the DEVDB panel. But I remembered, in SSMS, I need to check the checkbox "Trust Server Certificate" because my development environment uses a self-signed cert as is the default with SqlServer 2022. That could be the cause of the failure...

How can I add that to my configuration?

I'm really wanting the MCP server but could benefit from your tools window also! Thanks for any assistance you can provide.

Screenshots

Additional context

No response

[uptondev]

...And I get this in the output window...
[Connector - Config file provider] Attempting to connect to database: dialect=mssql, host=DESKTOP-YODA\SQLEXPRESS, port=1433, username=someROuser, database=T*****
[Init] Config File useable in workspace: no

[uptondev]

I see "tedious" supports "trustServerCertificate" in connection config object: https://github.com/tediousjs/tedious/blob/master/src/connection.ts Not sure about "knex"...

[uptondev]

I don't really know ts but maybe this line 119 in config-file-provider.ts is not allowing me to pass in the options object that knex (and tedious) accept -

async function mssqlConfigResolver(mssqlConfig: MssqlConfig): Promise<EngineProviderCache | undefined> {
	const connection = await getConnectionFor('Config file provider', 'mssql', mssqlConfig.host, mssqlConfig.port, mssqlConfig.username, mssqlConfig.password, mssqlConfig.database, false)

I tried updating my config to...

{
   "name": "My Sql Server",
   "type": "mssql",
   "host": "DESKTOP-YODA\SQLEXPRESS",
   "port": 1433,
   "username": "someROuser",
   "password": "someROuserPwd",
   "database": "TestDatabase",
   "options": {
      "trustServerCertificate": true
   }
}

Also, lines 7-20 in connector.ts would need amending I believe.

[traycerai]

Plan

Observations

Currently, the MSSQL connection path in DevDb uses a fixed signature: host, port, user, password, database, and a hard-coded boolean flag. There’s no mechanism to supply a driver-level options object (which Knex and the Tedious driver expect for flags like trustServerCertificate). The JSON schema for .devdbrc doesn’t define an options property, though it permits additional properties by default. Neither the TypeScript types nor the config-file provider hook into any extensible options bag, so connection creation via getConnectionFor cannot accept or forward certificate-trust flags.

Approach

1. Extend the MssqlConfig type to include an optional options field for arbitrary key/value pairs. 2. Update the JSON schema to document this new options block under the MSSQL section. 3. Modify mssqlConfigResolver to extract options from the config and pass it to getConnectionFor. 4. Change getConnectionFor to accept an options argument and merge it into the Knex connection object under connection.options when dialect === 'mssql'. 5. Add a README example showing how to set trustServerCertificate in .devdbrc.

Reasoning

I reviewed the config-file provider, connector, JSON schema, test suite, and Knex/Tedious best practices. I confirmed that no existing hook exists for driver options, that Knex passes an options object directly to Tedious, and that adding options will solve the self-signed certificate trust issue without breaking existing configs. The plan arranges changes in logical order: types → schema → resolver → connector → docs.

Proposed File Changes

📄 src/types.ts ^(MODIFY) 🔗

References

• 📄 src/types.ts ^(MODIFY)

Add an optional options?: Record<string, unknown> property to the MssqlConfig interface (alongside type, host, port, etc.) so that users can specify driver flags like trustServerCertificate.

📄 schemas/devdbrc.json ^(MODIFY) 🔗

References

• 📄 schemas/devdbrc.json ^(MODIFY)

In the MSSQL properties block, insert:

"options": { "type": "object", "description": "Driver options for MSSQL, e.g. `trustServerCertificate`", "additionalProperties": true }
``` to document the new field while allowing arbitrary keys.

📄 src/providers/config-file-provider.ts ^(MODIFY) 🔗

References

• 📄 src/providers/config-file-provider.ts ^(MODIFY)

Locate the mssqlConfigResolver call to getConnectionFor and insert the new options argument before the hard-coded boolean. Pseudocode:

getConnectionFor(
  'Config file provider',
  'mssql',
  host, port, username, password, database,
  mssqlConfig.options,    // ← pass through options
  false
)

📄 src/services/connector.ts ^(MODIFY) 🔗

References

• 📄 src/services/connector.ts ^(MODIFY)

Update getConnectionFor signature to accept options?: Record<string, unknown> just before notifyOnError. In the Knex connection builder, merge options under connection.options when dialect === 'mssql', so that it becomes:

const conn = { host, port, user, password, database };
if (dialect === 'mssql' && options) conn.options = options;
knex({ client: dialect, connection: conn });

📄 README.md ^(MODIFY) 🔗

References

• 📄 README.md ^(MODIFY)

Add an example under “Connection Settings” showing .devdbrc with an options block:

{
  "type": "mssql",
  // ... other fields ...
  "options": {
    "encrypt": true,
    "trustServerCertificate": true
  }
}

Diagram

sequenceDiagram
    User->>.devdbrc: specifies options
    ConfigFileProvider->>getConnectionFor: include options argument
    getConnectionFor->>Knex: merge options into connection
    Knex->>Tedious: receives cert-trust flags

Loading

Import In IDE

Developer Humor

"Trust in certificates you produce yourself? Sounds like a great plan for when you can’t trust anyone else! 😜"

---

Execution Information

Branch: main
Commit: 899f172

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[damms005]

@traycerai branch:main

[damms005]

@uptondev please upgrade to the latest version. The API is exactly as you described it!

{
	"name": "My MSSQL database",
	"type": "mssql",
	"host": "localhost",
	"port": "1433",
	"username": "sa",
	"password": "YourPassword123",
	"database": "master",
	"options": {
		"trustServerCertificate": true
	}
}

[uptondev]

The new version worked for me. Note that sql express users should not use the host config I showed above due to tedious issues with instance names. See this... tediousjs/tedious#118 I followed Cottin's advice to update my sql express configuration to use default port.

Thanks