[midPoint] Resource object consistency/connectorErrorCriticality doesn't work as expected

Oleksandr Nekriach o.nekriach at dynatech.lv
Mon Jul 5 16:29:15 CEST 2021


Hi guys,
Somebody does use consistency/connectorErrorCriticality settings in the Resource object (midpoint version 4.0.2 LTS)? For me, it seems not working. Maybe I have missed something. I have followed by this documentation
https://github.com/Evolveum/docs/blob/master/connectors/connid/1.x/connector-development-guide/index.adoc
Details:
Sometimes I need skip some connector errors that are not critical for my environment and I want to ignore  or mark them as Partial error.
My connector has the next consistency settings:
   <consistency>
      <c:connectorErrorCriticality>
        <c:network>partial</c:network>
        <c:schema>partial</c:schema>
        <c:generic>partial</c:generic>
    </c:connectorErrorCriticality>
   </consistency>
In my custom connector for these cases I return the next exception:
throw new InvalidAttributeValueException(myMessage);
In the log output I see expected stack trace:
org.identityconnectors.framework.common.exceptions.InvalidAttributeValueException: myMessage
2021-07-05 10:30:54,252 [PROVISIONING] [midPointScheduler_Worker-10] ERROR (com.evolveum.midpoint.provisioning.impl.ProvisioningServiceImpl): myMessage
com.evolveum.midpoint.util.exception.SchemaException: myMessage

But during reconciliation in IDM , I am still reciving a Fatal error instead of Partial error.
What have I missed? Please help.

Thank you in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20210705/26e557a6/attachment.htm>


More information about the midPoint mailing list