In Administration → Authentication the global user authentication method to Zabbix can be specified. The available methods are internal, HTTP and LDAP authentication.
Note that the authentication method can be fine-tuned on the user group level.
By default, internal Zabbix authentication is used globally. To change:
When done, click on Update at the bottom of the form.
HTTP or web server-based authentication (for example: Basic Authentication, NTLM/Kerberos) can be used to check user names and passwords. Note that a user must exist in Zabbix as well, however its Zabbix password will not be used.
|Enable HTTP authentication||Mark the checkbox to enable HTTP authentication.|
|Default login form||Specify whether to direct non-authenticated users to:
Zabbix login form - standard Zabbix login page.
HTTP login form - HTTP login page.
It is recommended to enable web-server based authentication for the
|Remove domain name||Enter the domain name that should be removed from the username.
|Case-sensitive login||Unmark the checkbox to disable case-sensitive login (enabled by default).
E.g. disable case-sensitive login and log in with, for example, 'ADMIN' user even if the Zabbix user is 'Admin'.
Note that with case-sensitive login disabled the login will be denied if multiple users exist in Zabbix database with similar alias (e.g. Admin, admin).
ErrorDocument 401 /index.php?form=defaultline to basic authentication directives, which will redirect to the regular Zabbix login form.
External LDAP authentication can be used to check user names and passwords. Note that a user must exist in Zabbix as well, however its Zabbix password will not be used.
While LDAP authentication is set globally, some user groups can still be authenticated by Zabbix. These groups must have frontend access set to Internal. Vice versa, if internal authentication is used globally, LDAP authentication details can be specified and used for specific user groups whose frontend access is set to LDAP.
Zabbix LDAP authentication works at least with Microsoft Active Directory and OpenLDAP.
|Enable LDAP authentication||Mark the checkbox to enable LDAP authentication.|
|LDAP host||Name of LDAP server. For example: ldap://ldap.zabbix.com
For secure LDAP server use ldaps protocol.
With OpenLDAP 2.x.x and later, a full LDAP URI of the form ldap://hostname:port or ldaps://hostname:port may be used.
|Port||Port of LDAP server. Default is 389.
For secure LDAP connection port number is normally 636.
Not used when using full LDAP URIs.
|Base DN||Base path to search accounts:
ou=Users,ou=system (for OpenLDAP),
DC=company,DC=com (for Microsoft Active Directory)
|Search attribute||LDAP account attribute used for search:
uid (for OpenLDAP),
sAMAccountName (for Microsoft Active Directory)
|Bind DN||LDAP account for binding and searching over the LDAP server, examples:
uid=ldap_search,ou=system (for OpenLDAP),
CN=ldap_search,OU=user_group,DC=company,DC=com (for Microsoft Active Directory)
Required, anonymous binding is not supported.
|Case-sensitive login||Unmark the checkbox to disable case-sensitive login (enabled by default).|
|Bind password||LDAP password of the account for binding and searching over the LDAP server.|
|Test authentication||Header of a section for testing|
|Login||Name of a test user (which is currently logged in the Zabbix frontend). This user name must exist in the LDAP server.
Zabbix will not activate LDAP authentication if it is unable to authenticate the test user.
|User password||LDAP password of the test user.|
TLS_REQCERT allowline to the /etc/openldap/ldap.conf configuration file. It may decrease the security of connection to the LDAP catalog.