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

node_discovered is triggered when you create a node from API #4987

Closed
nqb opened this issue Dec 6, 2019 · 4 comments · Fixed by #6527
Closed

node_discovered is triggered when you create a node from API #4987

nqb opened this issue Dec 6, 2019 · 4 comments · Fixed by #6527

Comments

@nqb
Copy link
Contributor

nqb commented Dec 6, 2019

When security event "Node discovered" is enable and you create a node, this security event is triggered.

To Reproduce

  1. Enable "Node discovered" security event
  2. Create a node
  3. Check your mail box or mail queue

Expected behavior
Only trigger this security event when a node has been discovered, not created in web admin. By
discovered, I mean data comes from DHCP or RADIUS request.

@jrouzierinverse
Copy link
Member

This has been the behavior for a while.
If a node is created it is considered discovered to the system.
Does it make sense to change this behavior?

@julsemaan
Copy link
Collaborator

I discussed this with @nqb and it doesn't seem like its a valid behavior.

This security event trigger was designed to alert you when a new node would come online on your network.

By applying this to the API, it makes it so importing 1000 nodes will generate 1000 security events and some devices may never actually come online on the system.

@nqb
Copy link
Contributor Author

nqb commented Dec 19, 2019

Completely agree with @julsemaan.

@julsemaan
Copy link
Collaborator

It seems we would need to skip the pf::dal::node::after_create_hook when creating the node via the API.

@jrouzierinverse, what would be the best way to do that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants