[midPoint] Is __NAME__ mandatory in createAttributes for create()?

Али Саад gerardo.saad at gmail.com
Wed Aug 26 09:42:56 CEST 2026


Hello,

I have a question regarding the ConnId CreateOp implementation in midPoint.

Is __NAME__ mandatory in the Set<Attribute> createAttributes passed to the
connector's create() method?

In particular, consider a target system where:

   - the object has only one identifier, e.g. id;
   - this id is generated by the target system during creation;
   - there is no separate login, username, name, DN, or any other value
   that could naturally be used as __NAME__ before the object is created.

In such a case, can midPoint call:

create(ObjectClass objectClass, Set<Attribute> createAttributes,
OperationOptions options)

without __NAME__ in createAttributes?

The connector would then create the object, receive the generated id from
the target system, return it as new Uid(id), and on subsequent reads return
the same value as both Uid and Name.

For example:

   - before create(): no Uid and no meaningful Name exist;
   - target system creates id = "4711";
   - create() returns Uid = "4711";
   - subsequent reads return Uid = "4711" and Name = "4711".

Is this supported by midPoint/ConnId, or must __NAME__ always be present in
createAttributes, even if it has no corresponding value in the target
system at creation time?

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


More information about the midPoint mailing list