[midPoint] define openldap connector schema with 2 or more object classes per entry

[Pálos Gustáv]

Hi Rene,

please instead of several <objectType> for each object class use only one
and set <auxiliaryObjectClass>, for example:

        <objectType>
            <kind>account</kind>
            <intent>default</intent>
            <displayName>Default Account</displayName>
            <default>true</default>
            <objectClass>ri:eduPerson</objectClass>
            <auxiliaryObjectClass>radiusprofile</auxiliaryObjectClass>
            <auxiliaryObjectClass>...</auxiliaryObjectClass>
...

best regards,

Gustav


2016-06-17 12:12 GMT+02:00 Rene Zeipelt <zeipelt at uni-wuppertal.de>:

> hello list,
> we try to define a schema for openldap entries which have attributes from
> several object classes (eduPerson, radiusprofile ...).
> so we stuck in handle one object class in schema handling definitions.
> reading schemes is no problem. midpoint is the latest
> version and openldap is a debian jessie 2.4.40. connector is
> com.evolveum.polygon.connector.ldap.LdapConnector 1.4.2.0.
> so define a complextype for own attributes with a nativeobjectclass
> __ACCOUNT__ ends in a "no OID for ..." error. so what we missing?
> thanks for any help.
> best regards Rene
>
>
>
> _______________________________________________
> 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/20160617/7f29ca0b/attachment.htm>