The topic of "providing windows ID / Password to SQL Server has come up a few different times so below is a solution that I found to work in most instances.
- Service accounts with Native SQL Server authentication is NOT supported (internal security rules, regulatory compliance etc.)
- Running SnapLogic using “IntegratedSecurity = true” would require every database to grant access to an individual robot / service account and didn’t allow specific user tracking
3rd party JDBC driver called jtds (http://jtds.sourceforge.net/) allows you to specify URL Properties and pass in account credentials.
You will need to upload this jar file into the SLDB and reference that within the account settings (see screen caps below).
On the SQL Server, you can see Windows Authentication selection for ID “SQLSvr_TESTING”
Account settings within SnapLogic for “SQL Server Account” type:
Account settings that need to be defined
- Referencing the JAR files uploaded to the SLDB
- The JDBC Driver Class should be set to net.sourceforge.jtds.jdbc.Driver
- URL Properties Defined:
useNTLMv2 = true
domain = [YourDomain]
instance = [InstanceName-OPTIONAL]
It’s important to stipulate that if the users windows password changes, they will need to come into SnapLogic and adjust the password in the account as well. By default, the SQL Server snaps will attempt to reconnect 3 times so you may get into a situation where the ID becomes locked out.