Bug 46431 - Account lockout via LDAP ppolicy on some UCS server doesn't cause UDM lockout on master
Summary: Account lockout via LDAP ppolicy on some UCS server doesn't cause UDM lockout...
Status: NEW
Alias: None
Product: UCS
Classification: Unclassified
Component: LDAP
Version: UCS 5.2
Hardware: Other Linux
: P3 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on: 31907 39817
Blocks:
  Show dependency tree / graph
 
Reported: 2018-02-26 18:50 CET by Arvid Requate
Modified: 2025-09-29 14:21 CEST (History)
5 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 3: A User would likely not purchase the product
User Pain: 0.171
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2018-02-26 18:50:13 CET 
Account lockout via LDAP ppolicy on some UCS server does not trigger UDM lockout on master. That's why 10_ldap/50ppolicy_account_lockout fails on a DC Backup.

See also Bug 31907 Comment 8 and following. The required UDM call code has been commented out in 70_ppolicy_udm_lock.patch.
Comment 1 Ingo Steuwer univentionstaff 2021-05-14 16:50:58 CEST 
should be still relevant for UCS 4.4