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

Allow to set more snmpv3 credentials #66

Open
stevie-sy opened this issue Jul 3, 2024 · 0 comments
Open

Allow to set more snmpv3 credentials #66

stevie-sy opened this issue Jul 3, 2024 · 0 comments
Labels

Comments

@stevie-sy
Copy link

The situation is now following:

  • for v2 traps it is possible to set multiple community strings for traps we accept.
  • for v3 traps you can configure only one v3 user wich credentials which everybody of our colleagues has to use for their maintaining hardware (storage, firewall, switches etc.). So it would be great to get the possibility to set more v3 credentials in one plugin definition.

The only workarround would be to configure more input plugins with diffrent v3 users incl. credentials. And every plugin definition has to listen to a diffrent port. If not we get an error message that this is not possible. But this isn't really nice if we can not use the standard trap port.

Why this would be great?

  1. For security reason! With the situation now, every department (storage, server, network, firewall) has to use the same credentials and this should be a no go! And we have some devices where the snmp credentials are the same for sending traps and requesting infos.
  2. Also a lot of our colleagues want to use - of course for security reason - the highest possible security protocol. e.g. AES256 / SHA256. But not every hardware manufacturer support the same protocols. So If we can only configure one v3 user (for everybody) you have to choose the absolute minium protocol (which may be insecure). That's often sha1/aes. But some devices like firewall doesn't support this old protocols any more.
@stevie-sy stevie-sy added the enhancement New feature or request label Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants