From 58da59854dbe24bd94999b33f94fb2b0196b9b23 Mon Sep 17 00:00:00 2001 From: Michael Friedrich Date: Thu, 5 Nov 2015 15:37:58 +0100 Subject: [PATCH] Change 'api setup' into a manual step while configuring the API fixes #10549 --- doc/9-icinga2-api.md | 9 ++++++--- icinga2.spec | 3 --- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/9-icinga2-api.md b/doc/9-icinga2-api.md index 5d45f2dbb..d0ce642c7 100644 --- a/doc/9-icinga2-api.md +++ b/doc/9-icinga2-api.md @@ -131,8 +131,11 @@ New installations of Icinga 2 will automatically set up a new `ApiUser` named `root` with an auto-generated password in the `/etc/icinga2/conf.d/api-users.conf` file. -You can manually invoke the CLI command `icinga2 api setup` which will generate -a new local CA, self-signed certificate and a new API user configuration. +Run the CLI command `icinga2 api setup` to generate certificates +and a new API user `root` with an auto-generated password in the +`/etc/icinga2/conf.d/api-users.conf` configuration file. + + # icinga2 api setup Once the API user is configured make sure to restart Icinga 2: @@ -144,7 +147,7 @@ You can test authentication by sending a GET request to the API: In case you get an error message make sure to check the API user credentials. -The curl parameter `-k` disables the master certificate verification. In order +The curl parameter `-k` disables certificate verification. In order to securely check each connection you'll need to pass the trusted CA certificate using the curl parameter`--cacert`: diff --git a/icinga2.spec b/icinga2.spec index 394ee1e2b..38b35968e 100644 --- a/icinga2.spec +++ b/icinga2.spec @@ -342,9 +342,6 @@ getent passwd %{icinga_user} >/dev/null || %{_sbindir}/useradd -c "icinga" -s /s %post bin -# install the api setup -%{_sbindir}/%{name} api setup - # suse %if "%{_vendor}" == "suse"