LDAP authentication with groups support (ZBXNEXT-276)

[ZBXNEXT-3834] LDAP authentication: LDAP servers list (Screen 1) Created: 2017 Apr 26  Updated: 2024 Apr 10  Resolved: 2022 Jun 17

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: None
Fix Version/s: None

Type: Change Request (Sub-task) Priority: Trivial
Reporter: Rostislav Palivoda (Inactive) Assignee: Zabbix Development Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue Links:
Sub-task
depends on ZBXNEXT-3831 LDAP authentication: Administrator se... Closed
Team: Team B
Sprint: Sprint 2, Sprint 3, Sprint 4, Sprint 5, Sprint 6, Sprint 90 (Jul 2022), Sprint 91 (Aug 2022), Sprint 92 (Sep 2022), Sprint 93 (Oct 2022), Sprint 94 (Nov 2022), Sprint 95 (Dec 2022), Sprint 96 (Jan 2023)
Story Points: 3

 Description   

Screen 1: LDAP servers list

Currently Zabbix LDAP authentication supports only one LDAP server. Some users consider it a limitation (e.g. it is not possible to configure secondary LDAP server for high availability, complex configurations may use several LDAP servers). While support of multiple LDAP servers is not yet planned, the overall LDAP user synchronization design tries to include multiple LDAP server perspective. Therefore we start from LDAP servers configuration screen.

LDAP servers overview

Name is a display name (for convenience, technically it is not necessary).
LDAP host shows a host name or IP address of LDAP server.
Searches is a link for going into LDAP searches configuration page, it also shows number of configured searches for this LDAP server.
Network timeout and Processing timeout - configurable parameters for LDAP library.
Status is a link for convenient enabling/disabling synchronization from this LDAP server. (It would be very inconvenient if the only method of temporary disabling a server was deleting it).


Generated at Fri May 16 10:13:11 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.