Time to stop using jTDS driver?

on Mar 13, 2020
Latest reply on Mar 16, 2020 by Pradeep Kadambar

Like • Show 0 Likes0
Comment • 10

If you haven't noticed the jTDS driver for MS SQL hasn't been updated in a while (almost 6 years). In the past jTDS type 4 driver had performance and stability benefits over Microsoft's JDBC driver (Download Microsoft JDBC Driver for SQL Server - SQL Server | Microsoft Docs ).

However it might be just the right time to stop using jTDS and use the Microsoft JDBC driver. Some of the reasons for changing the driver could be

Supportabilty - Microsoft's JDBC driver supports latest Java LTS versions 8 & 13
Security - jTDS does not support TLS1.2 which is current standard for secure connections
Better compatibility with MS SQL features

What to change?

Driver - com.microsoft.sqlserver.jdbc.SQLServerDriver
URL - jdbc.url=jdbc:sqlserver://dbhost:1433;databaseName=databasename;

This is not an endorsement but a forum for sharing your thoughts this topic.

Outcomes

10 Replies

Mostafa Helmy Mar 14, 2020 4:06 AM
I recall the jTDS driver was used to support NTLM authentication (windows logins) to SQL Server since the MS SQL Server JDBC driver did not support that. Do the MS SQL Server JDBC driver now support NTLM authentication?
Like • Show 0 Likes0
Actions
- Pradeep Kadambar @ Mostafa Helmy on Mar 14, 2020 8:41 PM
  Good point, the Microsoft JDBC driver supports the following authentication methods
  Basic or native
  NTLM
  Kerberos
  2 people found this helpful
  Like • Show 1 Like1
  Actions
  - Ian Staines @ Pradeep Kadambar on Mar 16, 2020 12:56 PM
    I would like to see a sample JDBC connection string for Windows Authentication. As far as I am aware we have never captured this information.
    Like • Show 1 Like1
    Actions
    - Pradeep Kadambar @ Ian Staines on Apr 1, 2020 12:14 PM
      Updated URL with SQL Server Driver v8.2.2 using NTLM
      
      1 person found this helpful
      Like • Show 1 Like1
      Actions
      - Justin Gregory @ Pradeep Kadambar on Mar 26, 2020 12:34 PM
        Hello Pradeep,
        
        Do you have any advice if we use the URL connection string above and it still fails to authenticate? I understand it would be a 3rd party incident...but where to begin trying to track down the resolution?
        Like • Show 0 Likes0
        Actions
        Pradeep Kadambar @ Justin Gregory on Mar 26, 2020 10:05 PM
        The above URL is from a working setup. Did you check the aveksaServer.log for more information on the failure ?
        Like • Show 0 Likes0
        Actions
        Pradeep Kadambar @ Justin Gregory on Mar 31, 2020 9:46 PM
        The version of driver shipped with IGL is very old. You will need to pickup the latest driver 8.2 and add it to ACM.
        
        You can follow the 000034189 - How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle KB to deploy the new driver.
        
        Don't forget to delete the old driver from the /tmp/customizeACM/aveksa.war/WEB-INF/LocalAgent/common/lib/ path before redeploying the application.
        Like • Show 0 Likes0
        Actions
Jamie Pryer Mar 16, 2020 8:09 AM
Thanks for sharing!
Should we maybe do these as a blog Pradeep?
lets sync
Like • Show 0 Likes0
Actions
Veera Chennawar Mar 31, 2020 2:49 PM
Can anybody confirm if the Microsoft driver supports integrated authentication? i am having authentication issues when i use the Microsoft driver with a domain account.
Like • Show 0 Likes0
Actions
- Pradeep Kadambar @ Veera Chennawar on Mar 31, 2020 9:36 PM
  FYI - Integrated authentication is only meant to work on Windows systems.
  Like • Show 0 Likes0
  Actions

Time to stop using jTDS driver?

Outcomes

Related Content

Recommended Content