TCal
New Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: We’ve updated Microsoft JDBC drivers for SQL Server that are bundled with ReadyAPI
Hi richie While trying a few things, I noticed the ms sql jar file (mssql-jdbc-9.2.1.jre15.jar) that comes with ReadyApi is version 9.2 - which was released in January 2021, and is NOT the Latest file available from MS. C:\Program Files\SmartBear\ReadyAPI-3.9.2\bin\ext\mssql-jdbc-9.2.1.jre15.jar So I went to get the 9.2 version of jdbc drivers to use that auth.dll file (mssql-jdbc_auth-9.2.1.x64.dll). IT WORKS! Anyone who may run into this issue - you can find the MS jdbc driver file here: https://docs.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver15#92 Long story short the readyapi Release notes are bit inaccurate. At this link: https://support.smartbear.com/readyapi/docs/general-info/version-history/features-added-to-ver-3-9-2.html It says: We’ve updated Microsoft JDBC drivers for SQL Server that are bundled with ReadyAPI. New driver version includes new features and bug fixes. The full list of changes you can find on the Microsoft’s web site. That link takes you to the 9.4 Version which that Auth.dll file is throwing the Complaints about - This driver is not configured for integrated authentication. https://docs.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver15#94 Thank you Tom1.7KViews1like0CommentsRe: We’ve updated Microsoft JDBC drivers for SQL Server that are bundled with ReadyAPI
Thank Rich, Yes you are correct in understanding my issue. Upgrade from ReadyAPI 3.9.1 to 3.9.2 and jdbc connections are failing. My understanding is that readyApi uses a self-contained Java - unless you specifically tell it to use your local installation. I will see about updating Java - but considering all you mention about java - it has been working with ReadyAPI for at least the last 10 version upgrades. I am on Windows 10 and use 64 bit versions of applications when available. My current java version is: java version "1.8.0_161" Java(TM) SE Runtime Environment (build 1.8.0_161-b12) Java HotSpot(TM) Client VM (build 25.161-b12, mixed mode, sharing) Tom1.7KViews0likes1CommentWe’ve updated Microsoft JDBC drivers for SQL Server that are bundled with ReadyAPI
I Installed ReadyApi 3.9.2 and none of my jdbc connections will work on various projects. The common Complaint is: Failed to get a connection for the specified properties; com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication. ClientConnectionId:a4128829-7b7c-4a14-b93a-0404c13e0064 I always copy over the existing sqljdbc_auth.dll to my existing ...SmartBear\ReadyAPI-3.9.2\bin folder during new version installs. I even downloaded the current new ms \sqljdbc_9.4\enu\auth\x64\mssql-jdbc_auth-9.4.0.x64.dll and have copied that to the ...SmartBear\ReadyAPI-3.9.2\bin folder, then restarted ReadyApi and I still get the Failed to get a connection message on multiple existing jdbc connections. I have tried renaming the file, I have tried using the old auth.dll file, I have tried using the new 9.4.0 auth.dll file and nothing is working. Connection strings generally look like: jdbc:sqlserver://SomeQADBServer:1433;databaseName=SomeQADB;IntegratedSecurity=true; Does anyone know how to get integrated Security to work with the new drivers? I am just now finding some different possible values to use for auth per the MS info at: https://docs.microsoft.com/en-us/sql/connect/jdbc/setting-the-connection-properties?view=sql-server-ver15 I will try the ActiveDirectoryIntegrated value. (Version 6.0+) This optional property indicates which authentication method to use for connection. Possible values are ActiveDirectoryIntegrated, ActiveDirectoryPassword, ActiveDirectoryMSI (version 7.2+), ActiveDirectoryInteractive (version 9.2+), ActiveDirectoryServicePrincipal (version 9.2+), SqlPassword, and the default NotSpecified. Thank you, Tom CSolved2.2KViews0likes3CommentsRe: NTLM Security no longer worki in v 1.2 nd 1.3
Hi Smartbear, We are also licensed users of SoapUI NG Pro. Has anyone at smartbear looked into this regression? It is failing in Ready API 1.1 and 1.3. Have you guys entered a bug report for this? There is a java nullPointerException in the error log, and with this issue our responses are failing with a 401 Unauthorized. It works fine in previous Pro versions of SoapUI prior to the Ready API introduction. <SoapUI Error Log> Fri May 08 09:00:27 CDT 2015:ERROR:java.lang.NullPointerException java.lang.NullPointerException at org.apache.http.impl.auth.NTLMEngineImpl.stripDotSuffix(NTLMEngineImpl.java:175) at org.apache.http.impl.auth.NTLMEngineImpl.convertDomain(NTLMEngineImpl.java:188) at org.apache.http.impl.auth.NTLMEngineImpl.access$500(NTLMEngineImpl.java:45) at org.apache.http.impl.auth.NTLMEngineImpl$Type1Message.<init>(NTLMEngineImpl.java:766) at org.apache.http.impl.auth.NTLMEngineImpl.getType1Message(NTLMEngineImpl.java:128) at org.apache.http.impl.auth.NTLMEngineImpl.generateType1Msg(NTLMEngineImpl.java:1298) at org.apache.http.impl.auth.NTLMScheme.authenticate(NTLMScheme.java:125) at org.apache.http.impl.auth.AuthSchemeBase.authenticate(AuthSchemeBase.java:124) at org.apache.http.client.protocol.RequestTargetAuthentication.process(RequestTargetAuthentication.java:105) at org.apache.http.protocol.ImmutableHttpProcessor.process(ImmutableHttpProcessor.java:108) at org.apache.http.protocol.HttpRequestExecutor.preProcess(HttpRequestExecutor.java:174) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$SoapUIHttpRequestExecutor.preProcess(HttpClientSupport.java:113) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:452) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:233) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:323) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:290) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:220) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119) at com.eviware.soapui.impl.wsdl.WsdlSubmit.submitRequest(WsdlSubmit.java:80) at com.eviware.soapui.impl.rest.RestRequest.submit(RestRequest.java:192) at com.eviware.soapui.impl.wsdl.teststeps.RestTestRequestStep.run(RestTestRequestStep.java:794) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:212) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:47) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:138) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:1) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:129) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) <SoapUI Log> Fri May 08 09:00:27 CDT 2015:ERROR:Exception in request: java.lang.NullPointerException Fri May 08 09:00:27 CDT 2015:ERROR:An error occurred [java.lang.NullPointerException], see error log for details Tom1.5KViews0likes1Comment