Hi @Alexandre Belhomme , tu use CLAPI to configure monitored ressources, you need a Centreon administrator account (“is admin” option in user’s definition).
You must use APIv2 that allow to use non admin (but with correct option enabled) .
https://docs-api.centreon.com/api/centreon-web/24.10/
Hi @Alexandre Belhomme , tu use CLAPI to configure monitored ressources, you need a Centreon administrator account (“is admin” option in user’s definition).
You must use APIv2 that allow to use non admin (but with correct option enabled) .
https://docs-api.centreon.com/api/centreon-web/24.10/
I’m sorry @Laurent , i meant regarding the use of the Centreon CLI. I figured that for the HTTP API V1 i need an admin and for others i can use the V2 API, but if I’m still using the CLI to (for example) load exports of the commands/services/hosts ?
to use CLAPI (Command Line API) you need a Centreon administrator account
I’m probably not clear, very sorry to reiterate. I’m not talking about the user used to autenticate to the internal API of Centreon, i’m talking about the local LINUX user executing the command.
I tried with:
- “centreon” user
- “root” user
- “apache” user (what works best so far)
- “centreon-engine” user
When running with some users like root, some generated files are created with the linux user permissions like within the /var/lib/centreon/centcore folder.
This is my struggle as there isn’t documentation onto what user to use in that context.