nchiluka (Customer) asked a question.
We are unable to establish connection to SQL Server (2016 sp3) from RSA IGL 7.5.2 P3 database connector.
Previously it worked with jTDS driver along with specified service account. Now attempted both jTDS and SQL Server to no avail. (error attached)
Previously it worked with jTDS driver along with specified service account. Now attempted both jTDS and SQL Server to no avail. (error attached)
when we added encrypt=false we were able to connect using SQL authentication, but Windows authentication is required so we added integratedSecurity=true but we faced the following error
com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication.
integratedSecurity needs to be false unless your client is running on a Windows server. I am not sure of the other requirements. What is the full JDBC URL you are trying?
Does anyone have a sample of a working JDBC string?
Here is a sample of the URL String
jdbc:sqlserver://SQLSERVER.EXAMPLE.com:1433;databaseName=Example;verifyServerCertificate=false&useSSL=true&requireSSL=true;
I think this is supposed to be the format but my lab is not working right now so I could not test.
jdbc:sqlserver://[server]:[port];database=[db];trustServerCertificate=true;integratedSecurity=true;user=[user without domain];password=[pw];authenticationScheme=NTLM;domain=[domain];authentication=NotSpecified
I am not sure about the username and password. The Microsoft documentation is really sparse but it implies you must specify this in the JDBC URL.
has it suddenly stopped working?
Was there any change on the endpoint (upgrade/update)?
Was there any change on GL (upgrade/update)?
@Boris.Lekumovich (RSA) I think the customer is just looking for a new recommendation for using windows authentication using the default native Microsoft SQL server JDBC driver. They do not have a history of success with this new driver.
Previously they were using an unsupported third party JDBC driver.