Skip to content

Commit 0305805

Browse files
99xtaljrybarczyker
andauthored
fix: add trustServerCertificate option to SqlServerConnectionOptions (#9985)
* fix: add missing 'trustServerCertificate' option to SqlServerConnectionOptions interface Closes: #8093 * docs: add `trustServerCertificate` description to mssql data source options docs * fix: consistency between jsdoc and docs --------- Co-authored-by: jrybarczyk <[email protected]>
1 parent 21a9d67 commit 0305805

File tree

2 files changed

+8
-0
lines changed

2 files changed

+8
-0
lines changed

docs/data-source-options.md

+2
Original file line numberDiff line numberDiff line change
@@ -378,6 +378,8 @@ Different RDBMS-es have their own specific options.
378378

379379
- `options.appName` - Application name used for identifying a specific application in profiling, logging or tracing tools of SQL Server. (default: `node-mssql`)
380380

381+
- `options.trustServerCertificate` - A boolean, controlling whether encryption occurs if there is no verifiable server certificate. (default: `false`)
382+
381383
- `options.debug.packet` - A boolean, controlling whether `debug` events will be emitted with text describing packet
382384
details (default: `false`).
383385

src/driver/sqlserver/SqlServerConnectionOptions.ts

+6
Original file line numberDiff line numberDiff line change
@@ -278,6 +278,12 @@ export interface SqlServerConnectionOptions
278278
* (default: node-mssql)
279279
*/
280280
readonly appName?: string
281+
282+
/**
283+
* A boolean, controlling whether encryption occurs if there is no verifiable server certificate.
284+
* (default: false)
285+
*/
286+
readonly trustServerCertificate?: boolean
281287
}
282288

283289
/**

0 commit comments

Comments
 (0)