Non-Windows Platform Connection String Error to Sql Server using Windows Authentication about databaseconnector

[schuemie]

Hi @jose-alvarado-guzman ,

The use of the JTDS driver is discouraged because it messes up dates. Do you need to specify the Windows domain of your user? If not, you can use the Microsoft JDBC driver instead (even without the integrated security).

[jose-alvarado-guzman]

Hi @schuemie,

Thanks for your response, I tried with and without the domain but neither way the server was able to authenticate me. The exceptions were entrusted domain and login failed respectively. According to the following Microsoft Developer post when connecting to Sql Server using Windows Authentication from a non-Windows platform the connection string needs the integrated security parameter set to true, the authentication schema needs to be set to JavaKerberos and the JDBC driver should be version 4.0 or above. This also requires configuring Kerberos which I had never done before and was trying to avoid using the jtds driver. Is using Kerberos the only way to authenticate from non-windows platforms to SQL Server using Windows Authentication since jtds is discouraged?

[schuemie]

Hi @jose-alvarado-guzman ,

If you don't need to provide the domain, you should be able to log in without integrated security. Did you try not providing the connection string but just setting the dbms, server, (port), user, and password arguments of either createConnectionDetails or connect?

[jose-alvarado-guzman]

Hi @schuemie,

Yes I tried using the createConnectionDetail function setting the dbms, server, port, user and password without the domain and then passing that object to the connect function but the login failed.

[schuemie]

You said you managed to connect with RJDBC and jtds. Do you think you could try making it work through RJDBC with the Microsoft JDBC driver instead?