I have set up an identity (with username: MYDOMAINNAME backslash myusername) and a sql server connection (MS-SQL Server using generic driver) but am getting an error when a connection is attempted.
I can log onto the SQL Server itself with SSMS and see in the logs that the login is failing with this error:
Reason: Attempting to use an NT account name with SQL Server Authentication
I see no way in the DB CONNECTION 2 configuration screen to specify to use Integrated Authentication. From posts I've read here, entering the username in the form domain\username will cause it to use integrated authentication, but that seems to not be the case.
This is a deep pile of issues, so I'll try to summarize.
I haven't had time to investigate further, but in initial testing we also had some serious problems with DB Connect 2 using integrated authentication. We could not seem to make it work regardless of how we configured things.
We have 20 or 30 inputs of various sorts (both integrated and local auth) against SQL server in DB Connect v1 with nary a problem. But in v2, we can't get a one of those to work no matter how we try to configure them. Switching those inputs to a local SQL auth works perfectly regardless of v1 or v2.
Not an ideal solution, but again, we haven't had the time to look into it further and we'll get it working before we start actually deploying things using v2.