Choosing the Authentication Method
With Icinga Web 2 you can authenticate against Active Directory, LDAP, a MySQL or a PostgreSQL database or delegate authentication to the web server.
Authentication methods can be chained to set up fallback authentication methods or if users are spread over multiple places.
Authentication methods are configured in the INI file config/authentication.ini.
Each section in the authentication configuration represents a single authentication method.
The order of entries in the authentication configuration determines the order of the authentication methods. If the current authentication method errors or if the current authentication method does not know the account being authenticated, the next authentication method will be used.
For delegating authentication to the web server simply add autologin to your authentication configuration:
[autologin]
backend = external
If your web server is not configured for authentication though, the autologin section has no effect.
The following example will show you how to enable external authentication in Apache using Basic access authentication.
Creating Users
To create users for basic access authentication you can use the tool htpasswd. In this example .http-users is
the name of the file containing the user credentials.
The following command creates a new file with the user icingaadmin. htpasswd will prompt you for a password.
If you want to add more users to the file you have to omit the -c switch to not overwrite the file.
sudo htpasswd -c /etc/icingaweb2/.http-users icingaadmin
Configuring the Web Server
Add the following configuration to the <Directory> Directive in the icingaweb.conf web server configuration file.
AuthType Basic
AuthName "Icinga Web 2"
AuthUserFile /etc/icingaweb2/.http-users
Require valid-user
Restart your web server to apply the changes.
If you want to authenticate against Active Directory or LDAP, you have to define a LDAP resource which will be referenced as data source for the Active Directory or LDAP configuration method.
| Directive | Description |
|---|---|
| backend | ldap |
| resource | The name of the LDAP resource defined in resources.ini. |
| user_class | LDAP user class. |
| user_name_attribute | LDAP attribute which contains the username. |
| filter | LDAP search filter. |
Example:
[auth_ldap]
backend = ldap
resource = my_ldap
user_class = inetOrgPerson
user_name_attribute = uid
filter = "memberOf=cn=icinga_users,cn=groups,cn=accounts,dc=icinga,dc=org"
Note that in case the set user_name_attribute holds multiple values it is required that all of its values are unique. Additionally, a user will be logged in using the exact user id used to authenticate with Icinga Web 2 (e.g. an alias) no matter what the primary user id might actually be.
| Directive | Description |
|---|---|
| backend | msldap |
| resource | The name of the LDAP resource defined in resources.ini. |
Example:
[auth_ad]
backend = msldap
resource = my_ad
If you want to authenticate against a MySQL or a PostgreSQL database, you have to define a database resource which will be referenced as data source for the database authentication method.
| Directive | Description |
|---|---|
| backend | db |
| resource | The name of the database resource defined in resources.ini. |
Example:
[auth_db]
backend = db
resource = icingaweb-mysql
For authenticating against a database, you have to import one of the following database schemas:
- etc/schema/preferences.mysql.sql (for MySQL database)
- etc/schema/preferences.pgsql.sql (for PostgreSQL databases)
After that you have to define the database resource.
Manually Creating Users
Icinga Web 2 uses the MD5 based BSD password algorithm. For generating a password hash, please use the following command:
openssl passwd -1 password
Note: The switch to
openssl passwdis the number one (-1) for using the MD5 based BSD password algorithm.
Insert the user into the database using the generated password hash:
INSERT INTO icingaweb_user (name, active, password_hash) VALUES ('icingaadmin', 1, 'hash from openssl');