<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello Ali,</p>
<p>answers are inline.</p>
<p>Best regards,</p>
<pre class="moz-signature" cols="72">--
Pavol Mederly
Interim Chief Product Officer
evolveum.com</pre>
<div class="moz-cite-prefix">On 09/04/2026 20:47, Али Саад via
midPoint wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKeUUK8QXmhHj=oS0AUJ-78NVYn3C0+r27vuYZ5d4DWaFFdC4Q@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<pre style="white-space:pre-wrap;color:rgb(0,0,0)">Hello again, repost again!
I have a question regarding midPoint provisioning behavior and ConnId
connectors.
As I understand, during update operations midPoint invokes updateDelta()
and only sends changed attributes (AttributeDelta set).
However, in my integration scenario the target system API requires some
attributes to be sent on every update request, even if they have not
changed.
For example:
- login (identifier)
- system/source field
- some mandatory attributes required by API contract
The problem is that these attributes are not always included in
AttributeDelta, since they are not modified.
My questions:
1. Is there a way to force midPoint to always include certain attributes in
updateDelta, even if they are unchanged?</pre>
</div>
</blockquote>
<p>I don't know of any.</p>
<p>There is a similar feature in asynchronous provisioning (AFAIK),
but that's a very specific case.</p>
<blockquote type="cite"
cite="mid:CAKeUUK8QXmhHj=oS0AUJ-78NVYn3C0+r27vuYZ5d4DWaFFdC4Q@mail.gmail.com">
<div dir="ltr">
<pre style="white-space:pre-wrap;color:rgb(0,0,0)">2. Would outbound mappings with strength=strong guarantee that these
attributes are always sent?</pre>
</div>
</blockquote>
No.
<blockquote type="cite"
cite="mid:CAKeUUK8QXmhHj=oS0AUJ-78NVYn3C0+r27vuYZ5d4DWaFFdC4Q@mail.gmail.com">
<div dir="ltr">
<pre style="white-space:pre-wrap;color:rgb(0,0,0)">3. Or is the recommended approach to enrich the request on the connector
side (service/mapper layer)?</pre>
</div>
</blockquote>
<p>Currently it seems to be to be the only option. I don't like it
very much, for the same reasons as you, but don't see an
alternative.</p>
<p>Maybe someone from the community has more experiences in this
area?</p>
<blockquote type="cite"
cite="mid:CAKeUUK8QXmhHj=oS0AUJ-78NVYn3C0+r27vuYZ5d4DWaFFdC4Q@mail.gmail.com">
<div dir="ltr">
<pre style="white-space:pre-wrap;color:rgb(0,0,0)">I would like to understand what is considered a best practice in such
scenarios.
I am trying to avoid mixing transport-level requirements (API contract)
with business logic inside the connector, so I am looking for the most
appropriate architectural approach.</pre>
</div>
</blockquote>
<br>
<blockquote type="cite"
cite="mid:CAKeUUK8QXmhHj=oS0AUJ-78NVYn3C0+r27vuYZ5d4DWaFFdC4Q@mail.gmail.com">
<div dir="ltr">
<pre style="white-space:pre-wrap;color:rgb(0,0,0)">
Thank you.</pre>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
midPoint mailing list
<a class="moz-txt-link-abbreviated" href="mailto:midPoint@lists.evolveum.com">midPoint@lists.evolveum.com</a>
<a class="moz-txt-link-freetext" href="https://lists.evolveum.com/mailman/listinfo/midpoint">https://lists.evolveum.com/mailman/listinfo/midpoint</a>
</pre>
</blockquote>
</body>
</html>