Bug 26384 - Referential Integrity Configuration Overlay Modul
Referential Integrity Configuration Overlay Modul
Status: RESOLVED DUPLICATE of bug 48956
Product: UCS
Classification: Unclassified
Component: LDAP
UCS 4.2
All Linux
: P4 enhancement (vote)
: ---
Assigned To: UCS maintainers
:
Depends on: 11980
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-07 07:31 CET by Stefan Gohmann
Modified: 2019-03-13 13:36 CET (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
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?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Further conceptual development, Release Goal
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2012-03-07 07:31:15 CET
Wir sollten die Integration prüfen. Ggf. können wir dann einiges an UDM Implementierung entfernen.


+++ This bug was initially created as a clone of Bug #11980 +++

(In reply to comment #1)
> Vielleicht könnte man sich in diesem Zusammenhang mal dieses LDAP Overlay
> anschauen:
> 
> "11.11.2. Referential Integrity Configuration" auf
> http://www.openldap.org/doc/admin24/overlays.html
Comment 1 Stefan Gohmann univentionstaff 2012-03-22 08:50:27 CET
Wichtig ist, dass rootdn gesetzt wird. Die Änderungen werden normal getriggert und landen somit auch im Notifier als eigenständige Änderung.
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:39:56 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Florian Best univentionstaff 2019-03-13 13:36:18 CET

*** This bug has been marked as a duplicate of bug 48956 ***