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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: