With versions 25.07 Cloud/24.10.9 onPrem, which mark the end of the Beta phase for the Centreon Monitoring Agent, agent/poller communication security has been strengthened.
Agent configuration via the interface or API now requires a valid authentication token.
To avoid disrupting configurations already in place at the time of the update (and therefore without tokens), TLS connections without tokens are still tolerated.
This will no longer be the case in 25.10
Any secure connection without a valid token will be refused by the poller and agent.
Therefore, before migrating to 25.10, for each existing agent configuration without a token, you will have to :
Generate a Token
In Administration > Authentication tokens, create a token with the Centreon monitoring agent type, with the expiry time of your choice (or without expiry).
Copy this token to the clipboard, from the creation screen or the token list.
Apply the token to the agent configuration on the central server
- In Configuration > Collectors > Agent configuration, for the existing entries, fill in the Authentication token field with the created token and validate.
- Export the configuration by restarting Engine.
Apply the token to the agent configuration on the host
- On the host, in the agent configuration, fill in the token field with the generated token.
- On Windows: in the installer, in the registry (\HKEY_LOCAL_MACHINE\SOFTWARE\Centreon\CentreonMonitoringAgent) or using the command line.
- On Linux: in /etc/centreon-monitoring-agent/centagent.json.
- Restart the agent.