Bug 44423 - handler is not run on modification if module filter only matches old object
handler is not run on modification if module filter only matches old object
Status: NEW
Product: UCS
Classification: Unclassified
Component: Listener (univention-directory-listener)
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-20 19:52 CEST by Arvid Requate
Modified: 2018-11-26 14:54 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional):
Max CVSS v3 score:
requate: Patch_Available+


Attachments
check_filter_also_against_old.patch (638 bytes, patch)
2017-04-20 19:52 CEST, Arvid Requate
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2017-04-20 19:52:58 CEST
Created attachment 8790 [details]
check_filter_also_against_old.patch

While checking Bug 33846 I found that the listener doesn't run a module handler on object modification if the module specifies a filter and the filter only matches the old object, but not the new one.

The listener simply only checks the filter against the new object, not against the old one. The attached patch may fix this.