You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to connect to a SQL Server Database using kerberos authentication from a Linux host.
Connection string I use is : Server=XX.XX.XX.XX,1433;Database=YYYYYY;trustedConnection=true;trustServerCertificate=true
(host name resolution didn't work)
returned error is : http://localhost:4177: Login failed for user ''.
It seems that the trustedConnection parameter is completly ignored.
Is integrated authentication on SQL Server Database supported by the gateway ?
The text was updated successfully, but these errors were encountered:
Hi @frederic-luce
Thanks for raising this.
The authentication part is handled by the connector, can you try to run the connect.test.ts and see how it goes?
If you can find a working setup (with the second test), I can make the change in the connector.
(as I don't have an SQL Server with kerberos, I can't test on my side)
Or we can setup a meeting to debug this together if you want.
In any way, you will have to checkout the repo and run the JS test on your machine.
I tried to connect to a SQL Server Database using kerberos authentication from a Linux host.
Connection string I use is :
Server=XX.XX.XX.XX,1433;Database=YYYYYY;trustedConnection=true;trustServerCertificate=true
(host name resolution didn't work)
returned error is :
http://localhost:4177: Login failed for user ''.
It seems that the trustedConnection parameter is completly ignored.
Is integrated authentication on SQL Server Database supported by the gateway ?
The text was updated successfully, but these errors were encountered: