11.26 Driver Loses An Event That Does Not Have class-Name

Issue: When you send an event to the Active Directory driver through the driver shim, the event is dropped without an error returned from the driver, the shim, or the engine. The lost event is not detected without checking explicitly. The following event is sent to the Active Directory shim:

<modify dest-dn="cn=FACSN Users,ou=FACSN users,OU=Units,DC=its,DC=cads,DC=ORG" event-id="testserver01#20171016161104#1#1:4f1bc979-33b2-43bb-84ea-79c91b4fb233">
  <modify-attr attr-name="member">
    <add-value>
      <value type="string">cn=testuser,ou=FACSN users,OU=Units,DC=its,DC=cads,DC=ORG<
DirXML: [10/16/17 10:11:04.41]: /value>
    </add-value>
  </modify-attr>
</modify>

The Remote Loader trace shows the following text that indicates that there is an event, but the class-name is missing:

DirXML: [10/16/17 10:11:04.55]: ADDriver: parse command
  className
  destDN       cn=FACSN Users,ou=FACSN users,OU=Units,DC=its,DC=cads,DC=ORG
  eventId      testserver01#20171016161104#1#1:4f1bc979-33b2-43bb-84ea-79c91b4fb233
  association
DirXML: [10/16/17 10:11:04.55]: ADDriver: parse modify class =
DirXML: [10/16/17 10:11:04.57]: Loader: subscriptionShim->execute() returned:
DirXML: [10/16/17 10:11:04.57]: Loader: XML Document:
DirXML: [10/16/17 10:11:04.57]: <nds ndsversion="8.7" dtdversion="1.1">
        <source>
                <product version="4.0.2.1" asn1id="" build="20170106_120000" instance="\ORG-IDV\ORG\services\ORG-VaultDriverSet\ORG-CADS">AD</product>
                <contact>NetIQ Corporation</contact>
        </source>
        <output>
                <add-association dest-dn="\ORG-IDV\ORG\data\users\employees\testuser" dest-entry-id="342222" event-id="testserver01#20171016161104#1#1:4f1bc979-33b2-43bb-84ea-79c91b4fb233">52b7c854d68c2a439be0bbb8fa597332</add-association>
                <status level="success" event-id="testserver01#20171016161104#1#1:4f1bc979-33b2-43bb-84ea-79c91b4fb233"/>
                <status level="success" event-id="testserver01#20171016161104#1#1:4f1bc979-33b2-43bb-84ea-79c91b4fb233"/>
        </output>
</nds>

Workaround: Ensure that you add a value for class-name when the custom event in Identity Manager policy is synthesized.