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

Fixes #21877: Hardening guide for Rudder #952

Conversation

amousset
Copy link
Member

@amousset amousset force-pushed the bug_21877/hardening_guide_for_rudder branch from 447f95e to 96c4965 Compare February 16, 2023 09:24
@amousset amousset requested a review from fanf February 16, 2023 09:24
@amousset amousset marked this pull request as draft February 16, 2023 09:24
@amousset
Copy link
Member Author

PR updated with a new commit

3 similar comments
@amousset
Copy link
Member Author

PR updated with a new commit

@amousset
Copy link
Member Author

PR updated with a new commit

@amousset
Copy link
Member Author

PR updated with a new commit

@amousset amousset requested review from Fdall and ncharles and removed request for fanf February 16, 2023 10:47
@amousset amousset marked this pull request as ready for review February 16, 2023 10:47
@amousset
Copy link
Member Author

PR updated with a new commit


Now you can set your policy server with `rudder agent policy-server mypolicyserver`
and the agent will only accept the connection if it matches the provided key hash.
This way, once the node sends its first inventory, if it matched the node id and certificate, it will be automatically accepted. Note that this creation call also allows pre-setting node properties.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is misleading - the node is already existing within Rudder

This way, once the node sends its first inventory, if the node id and certificate match the pre-provisionned entry, the node inventory will be update.
Please note that you can also pre-defined node properties using this API, to ensure that the pre-provisionned node is already in the correct groups

Copy link
Member

@ncharles ncharles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a really neat document
Some minor changes on wording are requested to make it more understandable

@amousset
Copy link
Member Author

PR updated with a new commit

@Normation-Quality-Assistant
Copy link
Contributor

OK, squash merging this PR

@Normation-Quality-Assistant Normation-Quality-Assistant merged commit 5b5cf89 into Normation:branches/rudder/7.3 Feb 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants