Bug 55148 – Support UDM hooks that are not bound to an extended attribute

Bug 55148 - Support UDM hooks that are not bound to an extended attribute


Summary:	Support UDM hooks that are not bound to an extended attribute

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UDM (Generic)
Version:	UCS 5.0
Hardware:	Other Linux

Importance:	P5 normal with 4 votes (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2022-08-30 09:40 CEST by Florian Best
Modified:	2022-08-30 09:42 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
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 Florian Best

2022-08-30 09:40:51 CEST

UDM hooks are currently bound to the existence of an extended attribute.

In many cases we need hooks which just run always for the given module.
Our current workaround is often to specify an invalid mapping e.g. objectClass=notexisting and filter it out in the ldap-modlist hook.