[v2.0.0-alpha.3] Unable to connect to SQL Server using Integrated Security

Hi, first of all congrats on the new release!

I was able to connect to an on-premises SQL Server 2016 (version 13.0.5865.1) using the `hasura/graphql-engine:v2.0.0-alpha.3` image, and SQL Server authentication mode (user/password).

My connection string is:

`Driver={ODBC Driver 17 for SQL Server};Server=myServerIPAddress;Database=myDatabase;UID=myUser;PWD=myPassword;`

The problem comes when I try to connect using Windows Authentication mode, also known as "Integrated Security=SSPI" with this connection string:

`Driver={ODBC Driver 17 for SQL Server};Server=myServerAddress;Database=myDataBase;Trusted_Connection=yes;`

As I write this, I realized that it could be that I need to configure Kerberos on the Hasura container, in order to Hasura engine to send the Windows credentials to the SQL Server instance.

Am I correct?

I so, could anybody point me to a link/article that explains how to configure Kerberos on the Hasura container?

Thank you very much!

Start with the reported hasura/graphql-engine:v2.0.0-alpha.3 container and compare the working SQL authentication connection string with the failing Trusted_Connection configuration. Investigate the issue's Kerberos and Windows Integrated Security questions; done would require a documented configuration or confirmed connection path for SQL Server integrated authentication.

Written by the indexing model from the issue text.