[midPoint-git] [Evolveum/midpoint] c1db69: Fix fetching incompatible associations

[mederly]

  Branch: refs/heads/master
  Home:   https://github.com/Evolveum/midpoint
  Commit: c1db69100fcf59fdb03b94be1f2347739f551e03
      https://github.com/Evolveum/midpoint/commit/c1db69100fcf59fdb03b94be1f2347739f551e03
  Author: Pavol Mederly <mederly at evolveum.com>
  Date:   2024-04-29 (Mon, 29 Apr 2024)

  Changed paths:
    M model/model-intest/src/test/java/com/evolveum/midpoint/model/intest/TestIntent.java
    A model/model-intest/src/test/resources/intents/resource-dummy-intents.xml
    M provisioning/provisioning-impl/src/main/java/com/evolveum/midpoint/provisioning/impl/shadows/ShadowedObjectConstruction.java

  Log Message:
  -----------
  Fix fetching incompatible associations

When having two account types, the first with an association defined
(account/IA), and second one without one (account/IB); and only ex-post
("after retrieval") classification using <classificationCondition>,
then searching for account/IA may return a shadow S of type account/IB
with value(s) of the association (if they really exist on the resource).

This is because the search for simulated associations is executed under
the definition of account/IA, not account/IB.

This commit adds extra code that removes such associations. Actually,
no real harm would be done even if they remained there, as these shadows
will be ignored by the synchronization task (that requested their fetching)
anyway.

Related to MID-9591.

(an adapter cherry-pick of 6c8ddc2fd1d44d44b6ef0bd49a2c29ece4b57742)



To unsubscribe from these emails, change your notification settings at https://github.com/Evolveum/midpoint/settings/notifications