Failure: Enable Integrated Security in the JDBC Connection | Community
Skip to main content
J
JonathanMe12
September 18, 2025
Solved

Failure: Enable Integrated Security in the JDBC Connection

  • September 18, 2025
  • 1 reply
  • 861 views

Hi, 

Using AEM forms JEE 6.5 service pack 23 installer, connecting to SQL Server 2023 when enabling integrated security we get the following error:

Caused by: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/IDP_DS

Adminui not able to be access and EAR files failed to deploy.

System works with SQL login account but not with Microsoft service account.

 

 

We have:

JBoss service login changed with new Windows account

Placed mssql-jdbc-13.2.0.jre11 file in Windows, system32, adobe\bin folders.

Edit Turnkey file with:<datasources>
<datasource jta="true" jndi-name="java:/IDP_DS" pool-name="IDP_DS" enabled="true" use-java-context="true" statistics-enabled="${wildfly.datasources.statistics-enabled:${wildfly.statistics-enabled:false}}">
<connection-url>jdbc:sqlserver://XXXX:65000;DatabaseName=XXXX;integratedSecurity=true;encrypt=false</connection-url>
<driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
<driver>sqlserver</driver>

 

JBoss service is running but having this error message in the Server log file:

WFLYEJB0034: Jakarta Enterprise Beans Invocation failed on component EjbTransactionCMTAdapter for method public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterLocal.doRequiresNew(com.adobe.idp.dsc.transaction.TransactionDefinition,com.adobe.idp.dsc.transaction.TransactionCallback) throws com.adobe.idp.dsc.DSCException: javax.ejb.TransactionRolledbackLocalException: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/IDP_DS.

 

Running Netstat command we see Established connection with port 65000

and we were able to connect data base with this service account but looks like is failing when its trying to deploy the files in the data base.

 

We are using  mssql-jdbc-13.2.0.jre11

Microsoft SQL data base 23

 

 

 

 

Best answer by HrishikeshKagne

Hi @jonathanme12 ,

Your JDBC connection with integratedSecurity=true is failing because AEM Forms JEE (running on JBoss/WildFly) cannot load the Microsoft SQL Server authentication DLL (mssql-jdbc_auth.dll) that is required when you use Windows Authentication.

 

SQL login works because it doesn’t need the native DLL.

 

Service account (Integrated Security) fails because the JDBC driver needs to call Windows libraries to authenticate.

 

Just putting the JDBC driver JAR (mssql-jdbc-13.2.0.jre11.jar) in the bin or system32 is not enough – you must also add the correct version of mssql-jdbc_auth-<version>-x64.dll.

 

1. Download the same version of the JDBC auth DLL that matches your JDBC driver (13.2.0 and JRE11, x64).

 

You’ll find it inside the Microsoft JDBC driver package (sqljdbc_<version>_enu.zip).

 

Example: mssql-jdbc_auth-13.2.0.x64.dll.

 

2. Copy the DLL into a folder that is in the Windows PATH or into:

 

<AEM Forms JEE>\jboss\bin

 

or C:\Windows\System32 (if JBoss runs as a service).

 

3. Ensure the JBoss service is running under the same Windows service account that has DB access.

 

4. Restart JBoss/WildFly.

After this, the integrated security connection should succeed, EARs will deploy, and AdminUI will load.

 

The error isn’t with your connection string It’s because the JDBC driver needs the auth DLL, which isn’t being found by JBoss. Add the correct DLL to the PATH and restart, and it will work

1 reply

HrishikeshKagne
Community Advisor
HrishikeshKagneCommunity AdvisorAccepted solution
Community Advisor
September 19, 2025

Hi @jonathanme12 ,

Your JDBC connection with integratedSecurity=true is failing because AEM Forms JEE (running on JBoss/WildFly) cannot load the Microsoft SQL Server authentication DLL (mssql-jdbc_auth.dll) that is required when you use Windows Authentication.

 

SQL login works because it doesn’t need the native DLL.

 

Service account (Integrated Security) fails because the JDBC driver needs to call Windows libraries to authenticate.

 

Just putting the JDBC driver JAR (mssql-jdbc-13.2.0.jre11.jar) in the bin or system32 is not enough – you must also add the correct version of mssql-jdbc_auth-<version>-x64.dll.

 

1. Download the same version of the JDBC auth DLL that matches your JDBC driver (13.2.0 and JRE11, x64).

 

You’ll find it inside the Microsoft JDBC driver package (sqljdbc_<version>_enu.zip).

 

Example: mssql-jdbc_auth-13.2.0.x64.dll.

 

2. Copy the DLL into a folder that is in the Windows PATH or into:

 

<AEM Forms JEE>\jboss\bin

 

or C:\Windows\System32 (if JBoss runs as a service).

 

3. Ensure the JBoss service is running under the same Windows service account that has DB access.

 

4. Restart JBoss/WildFly.

After this, the integrated security connection should succeed, EARs will deploy, and AdminUI will load.

 

The error isn’t with your connection string It’s because the JDBC driver needs the auth DLL, which isn’t being found by JBoss. Add the correct DLL to the PATH and restart, and it will work

Hrishikesh Kagane
    Terms & ConditionsAccessibility statement

    Loading footer...