[midPoint] Debugging assignment's referential integrity issues

[Rodrigo Yanis]

Hello all,

We've come across the following case involving issues in how midpoint
handles referential integrity in assignments and inducements. As for
version 3.4.1, the case is the following:
1. An object "A" is created and assigned / induced into another object "B"
2. Object "A" is then deleted from midpoint
3. Object "B" keeps the reference to object's "A" oid, even though it
doesn't exist anymore.
We replicated this in role to user assignments, role to role assignments,
role to role inducements.
Is there any automatic native mechanism for resolving this referential
errors?
If not, is there a way to attack the issue through the use of tasks?

Thanks,

*Rodrigo Yanis.*
Identicum S.A.
Jorge Newbery 3226
Tel: +54 (11) 4824-9971
ryanis at identicum.com
www.identicum.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170116/69edd1f4/attachment.htm>