Bug 46431 - Account lockout via LDAP ppolicy on some UCS server doesn't cause UDM lockout on master
Account lockout via LDAP ppolicy on some UCS server doesn't cause UDM lockout...
Status: NEW
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.3
Other Linux
: P3 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on: 31907 39817
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-26 18:50 CET by Arvid Requate
Modified: 2019-02-27 18:05 CET (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:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

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.