Microsoft SQL connection via Azure Active Directory Password - ADAL4J

[UseThat]

Hi,

I need help with connection to SQL Server on Azure platform. When I try to connect i got error:

Connection failure. You must change the Database Settings.

 java.lang.RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: Failed to load ADAL4J Java library for performing ActiveDirectoryPassword authentication.

   at org.talend.core.model.metadata.builder.database.JDBCDriverLoader.getConnection(JDBCDriverLoader.java:208)

   at org.talend.core.model.metadata.builder.database.ExtractMetaDataUtils.connect(ExtractMetaDataUtils.java:1146)

   at org.talend.core.model.metadata.builder.database.ExtractMetaDataFromDataBase.testConnection(ExtractMetaDataFromDataBase.java:315)

   at org.talend.metadata.managment.repository.ManagerConnection.check(ManagerConnection.java:290)

   at org.talend.repository.ui.wizards.metadata.connection.database.DatabaseForm$67.runWithCancel(DatabaseForm.java:4208)

   at org.talend.repository.ui.wizards.metadata.connection.database.DatabaseForm$67.runWithCancel(DatabaseForm.java:1)

   at org.talend.repository.ui.dialog.AProgressMonitorDialogWithCancel$1.runnableWithCancel(AProgressMonitorDialogWithCancel.java:77)

   at org.talend.repository.ui.dialog.AProgressMonitorDialogWithCancel$ARunnableWithProgressCancel$1.call(AProgressMonitorDialogWithCancel.java:161)

   at java.util.concurrent.FutureTask.run(Unknown Source)

   at java.lang.Thread.run(Unknown Source)

 Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Failed to load ADAL4J Java library for performing ActiveDirectoryPassword authentication.

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.getFedAuthToken(SQLServerConnection.java:4262)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.onFedAuthInfo(SQLServerConnection.java:4237)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.processFedAuthInfo(SQLServerConnection.java:4202)

   at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onFedAuthInfo(tdsparser.java:289)

   at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:125)

   at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:37)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:5173)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3810)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:94)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3754)

   at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7225)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:3053)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2562)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:2216)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:2067)

   at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1204)

   at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:825)

   at org.talend.core.model.metadata.builder.database.DriverShim.connect(DriverShim.java:41)

   at org.talend.core.model.metadata.builder.database.JDBCDriverLoader.getConnection(JDBCDriverLoader.java:199)

   ... 9 more

My Connection string looks like:

jdbc:sqlserver://mydb.database.windows.net;DatabaseName=table;authentication=ActiveDirectoryPassword

And matadata:

I don't know why I get that error. Is someone face with this problem?

Regards,

Mateusz

[manodwhb]

@not specified not specified​ , May be you need to use the ssh tunneling,since i have use to connect AWS RDS from my local Talend.

[hittustyle]

@not specified not specified​  Did you get resolution on above issue? We have verified all Jars with respect to Azure Active Directory Password authentication. In our case we are connecting to Azure SQL Server DB

[UseThat]

Issue has been solved by us, by switching login method to SQL Users autentication.