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.
November 16, 2021 at 6:30 AM
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.
November 16, 2021 at 7:32 AM
Post a Comment

Popular posts from this blog

NetIQ IDM - JDBC statemens using policy builder

Few examples of using JDBC statements using dirxml policies On the Output policy: Handling matching policies with operation-data support: < rule > < description > [DB] Convert Query to DDL doc </ description > < comment name = "author" xml:space = "preserve" > Maqsood Ali Bhatti </ comment > < comment name = "version" xml:space = "preserve" > 5 </ comment > < comment name = "lastchanged" xml:space = "preserve" > Dec 20, 2017 </ comment > < conditions > < and > < if-operation mode = "case" op = "equal" > query </ if-operation > </ and > </ conditions > < actions > < do-append-xml-element expression = ".." name = "jdbc:statement" /> < do-append-xml-element expression = "../jdbc:statement[las...
Post a Comment
Read more

NetIQ IDM - Strip unwanted group member values from current operation

This code example shows how to remove unwanted group members from current operation based on some business logic. Optimization group members add to avoid  "ALREADY_EXIST_VALUE" kind of errors. when IDM engine fails to do so. Here I am doing look up in AD for members, and for each added member from IDM if user is already member of AD group, i am just striping out current member value from the current operaiton. < do-set-local-variable name = "group-dn" scope = "policy" > < arg-string > < token-src-dn /> </ arg-string > </ do-set-local-variable > < do-set-local-variable name = "group-members" scope = "policy" > < arg-node-set > < token-dest-attr class-name = "Group" name = "Member" /> </ arg-node-set > </ do-set-local-variable > < do-trace-message > < arg-string ...
Post a Comment
Read more