driver-operation-data

<driver-operation-data> is used to allow policies to inject an additional custom data payload to be carried along with any event or command.

The content of the <driver-operation-data> can be any well formed XML but it is recommended that any elements and attributes used be placed in a custom namespace to avoid having them confused with standard DirXML operations.

The typical use for <driver-operation-data> is to be able to create a policy that supplies additional data on an operation that may be needed by the drivershim

Example

<driver-operation-data class-name="User" command="modify" src-dn="\IDMTREE\data\users\newuser1">
<request>
<url-token association="newuser1"/>
<header content-type="application/json"/>
<value>{"Title":[{"add":["Employee"]}]}</value>
</request>
</driver-operation-data>

1. Allowed Content

ANY

2. No Attributes

3. Content Rule

ANY

4. Parent Elements

add
  Add an object command/Object was added event.
add-association
  Add association command.
check-object-password
  Check password against an eDirectory object.
check-password
  Check password against eDirectory driver object.
delete
  Delete an object command/Object was deleted event.
instance
  Current state of an instance of an object.
modify
  Modify an object command/Object was modified event.
modify-association
  Modify association command.
modify-password
  Modify an object password command/Object password was modified event.
move
  Move an object command/Object was moved event.
query
  Query command.
query-ex
  Query command with result count limit.
remove-association
  Remove association command.
rename
  Rename an object command/Object was renamed event.

Top Elements || All Elements || Tree


NDS DTD