[midPoint] Debugging assignment's referential integrity issues

[Nicolas Rossi]

Hi guys, it is also happening in midPoint 3.5. We tried running Cleanup and
Validity Scanner tasks but the reference is still there. Is there any way
to fix this references ?

Thanks in advance !






Ing Nicolás Rossi
Identicum S.A.
Jorge Newbery 3226
Tel: +54 (11) 4552-3050
www.identicum.com

On Mon, Jan 16, 2017 at 1:01 PM, Rodrigo Yanis <ryanis at identicum.com> wrote:

> 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
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20170201/7f0d6c24/attachment.htm>