We need to start doing Windows based Auth for our SQL servers and found a video on Inductive University on how to set this up. In the process of walking through it I noticed our Ignition Server(8.3.6) has mssql-jdbc-7.2.1.jre11.jar this seems like an old driver. Should I be updating this driver on our server and if so, do Gateway updates not update this driver?
Also if I should update the driver what rev should I use?
I believe gateway updates carry forward your existing drivers, and if you delete the old driver (by deleting the .jar file in user-lib/jdbc within the installation directory), Ignition will default to using the bundled driver (9.4.0.jre11) after a restart. The bundled driver is at the system level, and your screenshot shows the core level.
What I would do is take a gateway backup, stop the gateway service, make a backup copy of your mssql-jdbc-7.2.1.jre11.jar file somewhere else and remove it from your installation directory, start the gateway service, then check config -> databases -> drivers for the Microsoft SQLServer JDBC driver (making sure it is 9.4.0.jre11). Check that all your SQL connections show as valid. From here I believe you could move into the Windows authentication portion.
This is great advice.
Note that this behavior, with the bundled JDBC driver files inside modules, is something new to 8.3. We're hoping to achieve a sane balance between keeping the drivers up to date and not risking breaking folk's systems quietly on upgrade. In all prior versions, the seeded JDBC drivers when you first installed were what you got in your gateway for the rest of time (and indeed, that's still the case if you're upgrading from older systems). Only brand new gateways, starting on 8.3 fresh, will be subject to us automatically upgrading the driver underneath you when the modules update. Unless you choose to copy from the 'system' collection to 'core', at which point you'll be in the same situation as all prior versions.
