Configuring DevTest with SQL Server 2022 (Integrated Security)

Products

• Service Virtualization

Issue/Introduction

This guide outlines the steps required to configure DevTest components to connect to SQL Server 2022 using Windows Integrated Security. These steps ensure compatibility by using the specific JDBC driver and native DLL versions required for SQL Server 2022.

Environment

All supported versions of DevTest

Resolution

1. Prerequisites & File Placement

To support SQL Server 2022 via Integrated Security, you must ensure version alignment between the JDBC JAR and the native authentication DLL (v13.2.1).

File	Destination
mssql-jdbc_auth-13.2.1.x64.dll	%DevTest_Home%\jre\bin\ on all DevTest servers
mssql-jdbc-13.2.1.jre11.jar	%DevTest_Home%\lib\shared\ — Registry, Coordinator, Simulator, and VSE
mssql-jdbc-13.2.1.jre11.jar	%DevTest_Home%\lib\dradis\ — Enterprise Dashboard only

⚠️ IMPORTANT — Multi-Server Note: If you are running a distributed DevTest environment across multiple machines, every server must have these files copied to their respective directories. Failure to do so will cause database connection failures and trigger Registry timeouts.

2. Component Configuration

A.  Identity Access Manager (IAM)

Open %DevTest_Home%\IdentityAccessManager\iam.properties and  update the connection properties : 

iam.db.vendor=mssql

iam.db.url=jdbc:sqlserver://<hostname>:<port>;databaseName=<IAM database name>;integratedSecurity=true;encrypt=false;trustServerCertificate=true

iam.db.user=<host or domain name>\<username>

iam.db.password=<leave this property blank>

B. Enterprise Dashboard (ED)

Open %DevTest_Home%\dradis.properties and update the connection string properties:

lisadb.internal.enabled=false


# MS SQL Server connection

dradis.db.url=jdbc:sqlserver://<hostname>:<port>;databaseName=<Registry database name>;integratedSecurity=true;encrypt=false;trustServerCertificate=true

dradis.db.user=<host or domain name>\<username>

dradis.db.password=<leave this property blank>

C. DevTest Registry & Core Components

Open %DevTest_Home%\site.properties and ensure the main repository properties point to your database:

lisadb.internal.enabled=false


# MS SQL Server connection

lisadb.pool.common.url=jdbc:sqlserver://<hostname>:<port>;databaseName=<Registry database name>;integratedSecurity=true;encrypt=false;trustServerCertificate=true

lisadb.pool.common.user=<host or domain name>\<username>

lisadb.pool.common.password=<leave this property blank>

💡Note on Password Properties: Leaving the password property completely blank after the = sign is correct for Integrated Security setups, as Windows handles authentication via the underlying Service Account identity.

3. Windows Service Account Configuration

When using a Windows account (integrated security), the Windows services for the DevTest components must be configured to start under the same Windows account used to access the external SQL Server databases.

Recommended service startup types:

• Identity Access Manager service — Automatic
• Enterprise Dashboard service — Automatic
• All other DevTest services — Automatic (Delayed Start)

⚠️ Reminder: In multi-server deployments, confirm mssql-jdbc_auth-13.2.1.x64.dll (in %DevTest_Home%\jre\bin\) and mssql-jdbc-13.2.1.jre11.jar (in %DevTest_Home%\lib\shared\) are present on every node before starting services — a missing copy on any server causes Registry connection timeouts.