Add support for Windows Authentication for direct connection to SQL Server instance

[TigerC10]

Component(s)

receiver/sqlserver

Is your feature request related to a problem? Please describe.

The new direct connection configuration options (#30297) require a hardcoded plaintext username/password combination in the config to achieve its connection with SQL Server. This is a security risk, and would require tighter controls around access to that file than is typical.

Describe the solution you'd like

Extend support for the direct connection configuration to be able to use Windows Authentication (such as NTLM, or WinSSPI - even krb5), so that the service account that runs the open telemetry collector can be granted access to the database. This would allow for the database server to grant access to the service account, to keep the open telemetry configuration clean of usernames/passwords.

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• receiver/sqlserver: @djaglowski @StefanKurek

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/sqlserver: @djaglowski @StefanKurek

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[TigerC10]

Is there a Security label we can add to this issue?