[midPoint] syncying attributes on multiples classes

[Jason Everling]

under the schema section like so,

   <schema>
      <generationConstraints>
         <generateObjectClass>ri:inetOrgPerson</generateObjectClass>
         <generateObjectClass>ri:groupOfNames</generateObjectClass>
         <generateObjectClass>ri:groupOfUniqueNames</generateObjectClass>
         <generateObjectClass>ri:organizationalUnit</generateObjectClass>
         <generateObjectClass>ri:bshpCourse</generateObjectClass>
         <generateObjectClass>ri:bshpGroup</generateObjectClass>
         <generateObjectClass>ri:bshpPerson</generateObjectClass>
         <generateObjectClass>ri:eduPerson</generateObjectClass>
         <generateObjectClass>ri:extPerson</generateObjectClass>
      </generationConstraints>
..
....
...
.....
   </schema>

then under schemaHandling for each objectType for example a group and a
person,

   <schemaHandling>
      <objectType>
         <kind>entitlement</kind>
         <intent>courseGroup</intent>
         <displayName>Course Registry Group</displayName>
         <default>true</default>
         <objectClass>ri:groupOfNames</objectClass>
 <auxiliaryObjectClass>ri:bshpCourse</auxiliaryObjectClass>
 <auxiliaryObjectClass>ri:bshpGroup</auxiliaryObjectClass>
.....
.....
      </objectType>
  <objectType>
         <displayName>Person Registry Account</displayName>
         <default>true</default>
         <objectClass>ri:inetOrgPerson</objectClass>
         <auxiliaryObjectClass>ri:bshpPerson</auxiliaryObjectClass>
         <auxiliaryObjectClass>ri:eduPerson</auxiliaryObjectClass>
         <auxiliaryObjectClass>ri:extPerson</auxiliaryObjectClass>
.....
.....
      </objectType>
   </schemaHandling>

after you modify the resource xml you would need to reimport and over-write
your current resource configuration, if not, remove the

      <cachingMetadata>
              ..
      </cachingMetadata>

and

       <definition>
        ...
        ...
        </definition>

sections and generate the updated schema.


JASON

On Tue, Dec 5, 2017 at 8:44 AM, Jeria, Esteban <esteban.jeria at cgi.com>
wrote:

> Hi,
>
> We have some custom classes in our LDAP with specific attributes that I
> would like to import/sync to midPoint.
>
> I didn't find any example how to do it so I tried different approaches by
> creating multiples <objectType> on the <schemaHandling> section or by
> specifying an <auxiliaryObjectClass> but they are just ignored when I run
> the sync or import task.
>
> So, how can I perform an import/sync of a LDAP resource  when the source
> attributes are coming from different object classes?
>
>
>
> *Esteban Jeria*
>
> esteban.jeria at cgi.com
>
> Sécurité - Gestion des Identités et des Accès / Security - Identity and
> Access Management
>
>
>
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20171205/39c2e2fa/attachment.htm>