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

[Radovan Semancik]

Hi,

LDAP always has just one structural object class (not counting the 
superclasses). If you need more object classes in LDAP then the 
additional object classes are almost certainly auxiliary object classes. 
MidPoint has full support for auxiliary object classes, however the 
documentation is currently missing. However, you may find some 
inspiration in this example: 
https://wiki.evolveum.com/display/midPoint/Unix+Story+Test

-- 
Radovan Semancik
Software Architect
evolveum.com



On 06/17/2016 12:12 PM, Rene Zeipelt wrote:
> 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/86bc237c/attachment.htm>