-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request support for NTLMv2 #3534
Comments
@vlastahajek Correct me if I'm wrong, still a little fuzzy on Windows authentication methods, this is supported now by your latest patch to go-mssqldb? |
@danielnelson, my patch didn't add any new authentication method. The issue was in wrong handshake of authentication messages, not in unsupported authentication method. |
@cdcox87 are you still interested in seeing this feature implemented? |
Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Page. Thank you! |
Feature Request
Request MSSQL input plugin support NTLMv2 for authentication.
Current behavior:
Currently it appears that the plugin for gathering Microsoft SQL metrics only supports NTLMv1 and Kerberos.
Desired behavior:
Support NTLMv2
Use case: [Why is this important (helps with prioritizing requests)]
More and more businesses are dropping NTLMv1 due to security vulnerabilities. Logging in via Kerberos may not always be possible and NTLMv2 would be used. This is specifically a use case for logging in using the credentials in a service account and not putting them in the configuration file.
The text was updated successfully, but these errors were encountered: