/
Connect to SQL Server Using Windows Authentication

Connect to SQL Server Using Windows Authentication

Connect to SQL Server Using Windows Authentication

Pulse supports connecting to Microsoft SQL Server using Windows Authentication (also known as Integrated Security), in addition to the standard SQL username/password approach. This allows the Pulse Application Server Windows service account to authenticate to SQL Server without storing credentials in Pulse.cfg.

Prerequisites

  • Microsoft SQL Server 2012 or later.

  • A dedicated Pulse database already created in SQL Server.

  • The Windows service account running the Pulse Application Server service must have db_owner (DBO) rights on the Pulse database.

Configuration

Step 1 — Grant SQL Server Access to the Service Account

  1. In SQL Server Management Studio, create or identify the Windows account used to run the Pulse Application Server service.

  2. Add this account as a SQL Server login.

  3. Grant the account db_owner access to the Pulse database.

Step 2 — Update Pulse.cfg

  1. Stop the Pulse Application Server service.

  2. Open conf/Pulse.cfg in a text editor.

  3. Configure the [SQLServer] section with the JDBC URL but leave UserName and Password blank:

[SQLServer] JDBCURL = localhost:1433;databaseName=Pulse;integratedSecurity=true UserName = Password =

The integratedSecurity=true parameter instructs the JDBC driver to use the Windows service account for authentication rather than SQL credentials.

  1. Save the file and start the Pulse Application Server service.

Step 3 — Deploy the SQL Server JDBC Authentication DLL

For Windows Authentication to work with the JDBC driver, the mssql-jdbc_auth DLL must be available on the server:

  1. Locate the DLL from the Microsoft JDBC Driver for SQL Server package (e.g. mssql-jdbc_auth-12.x.x.x64.dll).

  2. Place the DLL in one of the following locations:

    • The bin folder of the Pulse installation directory, or

    • A folder listed in the Windows system PATH environment variable.

  3. Restart the Pulse Application Server service.

Verifying the Connection

After restarting Pulse, check pulse.log for successful database connection messages. If Windows Authentication fails, the log will show a JDBC connection error specifying the authentication method used.

Notes

  • Windows Authentication only works when the Pulse Application Server service runs under a domain account — not the LocalSystem or NetworkService built-in accounts.

  • If the service account changes, SQL Server access must be re-granted to the new account.

  • The Password field in Pulse.cfg should remain blank when using Windows Authentication; Pulse will not attempt to use it.