From gerardo.saad at gmail.com  Thu Apr  9 20:47:03 2026
From: gerardo.saad at gmail.com (=?UTF-8?B?0JDQu9C4INCh0LDQsNC0?=)
Date: Thu, 9 Apr 2026 21:47:03 +0300
Subject: [Midpoint-dev] Repost again! [midPoint] Is it possible to force
 sending unchanged attributes in updateDelta (ConnId)?
Message-ID: <CAKeUUK8QXmhHj=oS0AUJ-78NVYn3C0+r27vuYZ5d4DWaFFdC4Q@mail.gmail.com>

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?

2. Would outbound mappings with strength=strong guarantee that these
attributes are always sent?

3. Or is the recommended approach to enrich the request on the connector
side (service/mapper layer)?

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.

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint-dev/attachments/20260409/43d66631/attachment.htm>

From gerardo.saad at gmail.com  Thu Apr  9 20:54:35 2026
From: gerardo.saad at gmail.com (=?UTF-8?B?0JDQu9C4INCh0LDQsNC0?=)
Date: Thu, 9 Apr 2026 21:54:35 +0300
Subject: [Midpoint-dev] MidPoint: Multiple object types from single ConnId
 ObjectClass using delineation filters
Message-ID: <CAKeUUK8NiZEG8U06C+B_a70528aVDVPrU6KCz02i6O2YHUhheg@mail.gmail.com>

In MidPoint, if a connector returns all accounts under a single ConnId
ObjectClass (e.g. ACCOUNT), can I define multiple object types (intents),
such as *default* and *admin*, and use delineation filters to classify
accounts between them?

Specifically: if out of 300 accounts only 9 have the ADMIN role, will
MidPoint load those 9 into the *admin* object type and the remaining 291
into the *default* one?

Or do filters only reduce the dataset instead of distributing objects
across object types?

About filter
https://docs.evolveum.com/midpoint/reference/support-4.9/resources/resource-configuration/schema-handling/delineation/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint-dev/attachments/20260409/188fa5eb/attachment.htm>

From rajuatikes at gmail.com  Tue Apr 21 15:05:28 2026
From: rajuatikes at gmail.com (Raju)
Date: Tue, 21 Apr 2026 18:35:28 +0530
Subject: [Midpoint-dev] Creating Resource
Message-ID: <CALH9i9CZrnmT4_yQR3pS=LJQ0Fj1OiOMMH5nQ3R1s_ADkinAxA@mail.gmail.com>

*Best practices for creating a new resource by using an existing resource
and replacing or removing some unique IDsThanks*

*Raju*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint-dev/attachments/20260421/49ad028a/attachment.htm>

