We are trying to add a user in ADAM/LDS. When it is just an effective
class (not User/inetOrgperson) it works fine. But if we need to add
attrs that are in Aux classes, it looks like the way the <add> event
gets structured,

<add-attr attr-name="objectClass">
<value type="string">eduPerson</value>
</add-attr>
<add-attr attr-name="objectClass">
<value type="string">newPilotPerson</value>
</add-attr>

Seems like it is not adding a second value, rather it is overwriting
each time. So we always get an object class violation.

Tried reformatting the XML to look more like:

<add-attr attr-name="objectClass">
<value type="string">eduPerson</value>
<value type="string">newPilotPerson</value>
</add-attr>

But you can't, since the shim adds the @class-name as an add-value of
object class as the first attribute in the event. And it happens in the
shim, so you cannot apply policy to try and fix it.

Is it possible to add a user in LDS/ADAM and Aux classes and attrs from
the aux classes in the same event?

This is surprising behavior, and not what we expected, but seems to be
what is happening. Does not seem to happen in the AD Driver in my
experience.

IDM 4.5.02 with latest AD shim.