Setting up Integrated Security for Active Directory

Liquibase Enterprise was formerly known as Datical DB.

Setting up Integrated Security for Active Directory

If you are using Microsoft SQLServer with Datical DB, you can use Integrated Security to authenticate the database connection. 

Setting Up Windows

Microsoft requires that the DLL major.minor.patch version must match exactly to the version of the driver being used by Liquibase Enterprise.

Ensure you are using these exact versions:

  • use mssql-jdbc_auth-13.2.1.<arch>.dll (for Liquibase Enterprise 9.0+)

  • use mssql-jdbc_auth-12.4.3.<arch>.dll (for Liquibase Enterprise 8.10.526 maintenance patch)

  • use mssql-jdbc_auth-12.4.0.<arch>.dll (for Liquibase Enterprise 8.5 to 8.10.479)

Additional versions found in instructions below

If you are using a version of Datical DB prior to 7.9 use the sqljdbc_auth.dll in place of  mssql-jdbc_auth-<version>.<arch>.dll

Integrated Security requires access to mssql-jdbc_auth-<version>.<arch>.dll This file needs to be accessible in the Windows System path.

If it is not already on your system, you can get it from the Datical DB installation directory.

  • Go to <datical-install>\LiquibaseDesktop\plugins\ (for older versions <datical-install>\DaticalDB\plugins\)

  • Copy com.datical.db.drivers.mssql_1.x.x.jar to a temporary directory and unzip it (<unzip directory>). 

    On Windows systems you can:

    o Use <java-install-path>\JAVA\jar.exe xf <name>.jar

    o Change the extension of the file from .jar to .zip and then unzip it. 

  • Go to <unzip directory>\auth\, then go to the folder for your version of the Java Virtual Machine (JVM).

  • Copy the appropriate dll to the C:\Windows\System32\ directory

    • If you are running a 32-bit JVM,

      • use mssql-jdbc_auth-13.2.1.x86.dll (for Liquibase Enterprise 9.0+)

      • use mssql-jdbc_auth-12.4.3.x86.dll (for Liquibase Enterprise 8.10.526 maintenance patch)

      • use mssql-jdbc_auth-12.4.0.x86.dll (for Liquibase Enterprise 8.5 to 8.10.479)

      • use mssql-jdbc_auth-8.4.1.x86.dll(for Liquibase Enterprise 7.9 to 8.4)

      • use sqljdbc_auth.dll (for Liquibase Enterprise versions prior to 7.9)

    • If you are running a 64-bit JVM

      • use mssql-jdbc_auth-13.2.1.x64.dll (for Liquibase Enterprise 9.0+)

      • use mssql-jdbc_auth-12.4.3.x64.dll (for Liquibase Enterprise 8.10.526 maintenance patch)

      • use mssql-jdbc_auth-12.4.0.x64.dll (for Liquibase Enterprise 8.5 to 8.10.479)

      • use mssql-jdbc_auth-8.4.1.x64.dll (for Liquibase Enterprise 7.9 to 8.4)

      • use sqljdbc_auth.dll (for Liquibase Enterprise versions prior to 7.9)

        Datical DB is installed with a 64-bit JVM that is used by default.

Enabling Integrated Security for the Database Connection

 

Using the datical.project file 

  1. In the datical.project file, for any databases where you wish to use Integrated Security, update the dbDef to include integratedSecurity="true".

  2. Remove any values for username and password for that dbDef.

    <dbDefs xsi:type="dbproject:SqlServerDbDef" name="DEV" driver="com.microsoft.sqlserver.jdbc.SQLServerDriver" hostname="demo-db1-win.liquibase.net" port="1433" contexts="DEV" labels="develop" scriptExecutionTimeout="120" dbDefsId="a8ec50d5-43b8-3bb7-9267-be6c6296248b" databaseName="BTR_DEV" integratedSecurity="true" applicationName="Datical DB"/>

Using the Datical DB GUI

  1. In the Datical DB GUI, select the Edit Connection link under the Status button for a database.





  2. In the SQL Server section, select Security: Integrated Security (screenshot a below). Or for DaticalDB versions 7.8 and below, click the Integrated Security checkbox (screenshot b below).


  3. Click Test Connection and verify that you successfully connect to the database

  4. Click OK when done

Integrated Security DbDef Setting Effect on Runtime Credentials Project Setting

If you have Integrated Security enabled for a DbDef, the setting overrides the project setting to enable runtime credentials for any DbDef where it is set

 

 

Copyright © Liquibase 2012-2026 - Proprietary and Confidential