Skip to main content

NetIQ IDM - Adding operation-data to subscriber command transformaiton custom commands




Recently i had to execute EOL cmdlets using psexecute though new NetIQ azure ad driver, since this operation is fire and forget in nature, i would like to track whole request and response for my own generated commands from subscriber command transofrmaiton policy, so i solved it by following policy:


<do-set-dest-attr-value direct="true" name="psexecute">
<arg-association> <token-resolve datastore="src"> <arg-dn> <token-text xml:space="preserve">{userref}</token-text> </arg-dn> </token-resolve> </arg-association> <arg-value type="string"> <token-local-variable name="cmdlet" /> </arg-value> </do-set-dest-attr-value> <do-append-xml-element expression="../modify[@direct]" name="operation-data" /> <do-set-xml-attr expression="../modify[@direct]/operation-data" name="prop.psexecute.Action"> <arg-string> <token-local-variable name="action" /> </arg-string> </do-set-xml-attr>

Comments

Casper said…
Where did you find information about @direct?

I've been searching for it, but until nothing shows up.
Geoffrey Carman said…
DTD defines it here:
https://www.netiq.com/documentation/identity-manager-developer/dtd-documentation/dirxmlscript/do-add-dest-attr-value.html

But in general it is a holdover from earlier IDM builds. Should be replaced with when="direct"

Was supposed to be deprecated at some point but never was, as far as I can tell.