Change 'api setup' into a manual step while configuring the API

fixes #10549
This commit is contained in:
Michael Friedrich 2015-11-05 15:37:58 +01:00
parent 7e5f5544fc
commit 58da59854d
2 changed files with 6 additions and 6 deletions

View File

@ -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` named `root` with an auto-generated password in the `/etc/icinga2/conf.d/api-users.conf`
file. file.
You can manually invoke the CLI command `icinga2 api setup` which will generate Run the CLI command `icinga2 api setup` to generate certificates
a new local CA, self-signed certificate and a new API user configuration. 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: 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. 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 to securely check each connection you'll need to pass the trusted CA certificate
using the curl parameter`--cacert`: using the curl parameter`--cacert`:

View File

@ -342,9 +342,6 @@ getent passwd %{icinga_user} >/dev/null || %{_sbindir}/useradd -c "icinga" -s /s
%post bin %post bin
# install the api setup
%{_sbindir}/%{name} api setup
# suse # suse
%if "%{_vendor}" == "suse" %if "%{_vendor}" == "suse"