A Forum reader recently asked:
“I need to send some extra data from one eDirectory driver to another to use in a policy. I’m using <operation-data> and it works well when it’s a query. The <operation-data> gets sent over to the other driver, and I can use it.
But when I send <operation-data> with a <modify> it gets stripped. Why does that happen? Is there any way to allow it to pass through?”
And here is the response from Ofer Gigi …
Operation Data is normally stripped by the engine, just before the XDS document is submitted to the driver shim.
To pass data between two interconnected eDir drivers, you could use a dummy attribute for the job. For example:
<rule> <description>Append a Dummy attr for Operation Data</description> <conditions> <and> <if-class-name mode="nocase" op="equal">user</if-class-name> <if-op-attr name="somthing" op="available"/> </and> </conditions> <actions> <do-set-dest-attr-value name="dummyAttrForOperationData"> <arg-value> <token-text xml:space="preserve">some Value To Pass</token-text> </arg-value> </do-set-dest-attr-value> </actions> </rule>
You can then handle the data in the remote driver policies. Note that depending on where in the remote Publisher policies you need that data, you might need to add this dummy attribute name to the remote Publisher filter.