Skip to content
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

Closed
cdcox87 opened this issue Dec 1, 2017 · 4 comments · Fixed by #6100
Closed

Request support for NTLMv2 #3534

cdcox87 opened this issue Dec 1, 2017 · 4 comments · Fixed by #6100
Labels
feature request Requests for new plugin and for new features to existing plugins waiting for response waiting for response from contributor

Comments

@cdcox87
Copy link

cdcox87 commented Dec 1, 2017

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.

@danielnelson danielnelson added the feature request Requests for new plugin and for new features to existing plugins label Dec 1, 2017
@danielnelson
Copy link
Contributor

@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?

@vlastahajek
Copy link
Contributor

@danielnelson, my patch didn't add any new authentication method. The issue was in wrong handshake of authentication messages, not in unsupported authentication method.
However, If needed I can look at this as well, I saw similar requests in go-mssqldb repo.

@danielnelson danielnelson reopened this Jul 15, 2019
@sspaink
Copy link
Contributor

sspaink commented Apr 26, 2022

@cdcox87 are you still interested in seeing this feature implemented?

@sspaink sspaink added the waiting for response waiting for response from contributor label Apr 26, 2022
@telegraf-tiger
Copy link
Contributor

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requests for new plugin and for new features to existing plugins waiting for response waiting for response from contributor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants