Bitbucket throws an no sqljdbc_auth in java.library.path in the logs

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

When starting Bitbucket Service, the following is shown on the atlassian-bitbucket.log:

1 2 3 4 5 2019-05-31 14:40:25,595 WARN [spring-startup] c.m.s.j.internals.AuthenticationJNI Failed to load the sqljdbc_auth.dll cause : no sqljdbc_auth in java.library.path 2019-05-31 14:40:39,543 ERROR [spring-startup] com.zaxxer.hikari.pool.HikariPool bitbucket - Exception during pool initialization. com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication. ClientConnectionId:2d4c895d-73f9-4193-8f9e-6b1af5193098 ... Caused by: java.lang.UnsatisfiedLinkError: no sqljdbc_auth in java.library.pathDiagnosis

Environment

  • Running Bitbucket with SQL Server on a Windows OS.

Cause

  • Bitbucket is configured to use windows auth, but the driver hasn't been renamed.

  • The JDBC string has integratedSecurity=true on its parameter, causing an issue.

Resolution

  • If the intention is to use Windows authentication, it may be necessary to rename the appropriate driver. This document has the detailed steps to follow.

  • Open $BITBUCKET_HOME/shared/bitbucket.properties file and remove the integratedSecurity=true parameter from the jdbc.url string and restart Bitbucket Server.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.