Skip to main content

How to convert any application-specific JSON to XDS format for NetIQ REST driver to consume


How to convert any application-specific JSON  to XDS format for NetIQ REST driver to consume


See tip: MessageValueTextToNetIQ


 <rule>  
  <description>Successfull poll-users command handler actions bases on trigger job;</description>  
  <conditions>  
  <and>  
   <if-operation mode="regex" op="equal">status</if-operation>  
   <if-xpath op="true">./driver-operation-data[@command="custom-IDM-JOB-GET-USERS"]</if-xpath>  
   <if-local-variable mode="nocase" name="StatusValue" op="equal">200</if-local-variable>  
  </and>  
  </conditions>  
  <actions>  
  <do-trace-message>  
   <arg-string>  
   <token-text xml:space="preserve">poll-users completed successfully; </token-text>  
   </arg-string>  
  </do-trace-message>  
  <do-set-local-variable name="StatusValue" scope="policy">  
   <arg-string>  
   <token-xpath expression="./driver-operation-data/response/value/@status"/>  
   </arg-string>  
  </do-set-local-variable>  
  <do-trace-message>  
   <arg-string>  
   <token-text xml:space="preserve">Status value =></token-text>  
   <token-local-variable name="StatusValue"/>  
   </arg-string>  
  </do-trace-message>  
  <do-set-local-variable name="MessageValue" scope="policy">  
   <arg-string>  
   <token-xpath expression="./driver-operation-data/response/value/@message"/>  
   </arg-string>  
  </do-set-local-variable>  
  <do-trace-message>  
   <arg-string>  
   <token-text xml:space="preserve">Status value =></token-text>  
   <token-local-variable name="MessageValue"/>  
   </arg-string>  
  </do-trace-message>  
  <do-set-local-variable name="MessageValueText" scope="policy">  
   <arg-string>  
   <token-xpath expression="./driver-operation-data/response/value/text()"/>  
   </arg-string>  
  </do-set-local-variable>  
  <do-set-local-variable name="MessageValueTextToNetIQ" scope="policy">  
   <arg-string>  
   <token-text xml:space="preserve">{ "totalResults": "$getCount$","results": [  
    </token-text>  
   <token-local-variable name="MessageValueText"/>  
   <token-text xml:space="preserve">]}</token-text>  
   </arg-string>  
  </do-set-local-variable>  
  <do-set-local-variable name="xmlInput" scope="policy">  
   <arg-string>  
   <token-base64-encode charset="UTF-8">  
    <token-replace-all regex="&amp;lt;" replace-with="&lt;">  
    <token-xml-serialize>  
     <token-text xml:space="preserve">&lt;status event-id="" level="success" type="driver-general">  
    &lt;driver-operation-data api="targetURL:" class-name="users" command="query" dest-dn="" event-id="" src-dn="">  
     &lt;response method="GET" url="">  
      &lt;header accept="application/json" content-type="application/json"/>  
    &lt;value message="OK" status="200">  
    $MessageValueTextToNetIQ$  
    &lt;/value>  
     &lt;/response>  
    &lt;/driver-operation-data>  
   &lt;/status></token-text>  
    </token-xml-serialize>  
   </token-replace-all>  
   </token-base64-encode>  
  </arg-string>  
  </do-set-local-variable>  
  <do-set-local-variable name="applicationContent" scope="policy">  
  <arg-string>  
   <token-xpath expression="rs:jsonToXDS($xmlInput)"/>  
  </arg-string>  
  </do-set-local-variable>  
  <do-if>  
  <arg-conditions>  
   <and>  
   <if-local-variable mode="nocase" name="applicationContent" op="not-equal"/>  
   </and>  
  </arg-conditions>  
  <arg-actions>  
   <do-set-local-variable name="xdscontent" scope="policy">  
   <arg-node-set>  
    <token-xml-parse>  
    <token-local-variable name="applicationContent"/>  
    </token-xml-parse>  
   </arg-node-set>  
   </do-set-local-variable>  
   <do-set-local-variable name="users" scope="policy">  
   <arg-node-set>  
    <token-xpath expression="$xdscontent/*//*[local-name()='value']"/>  
   </arg-node-set>  
   </do-set-local-variable>  
   <do-trace-message>  
   <arg-string>  
    <token-text xml:space="preserve">total users available =></token-text>  
    <token-xpath expression="count($users)"/>  
   </arg-string>  
   </do-trace-message>  
  </arg-actions>  
  <arg-actions/>  
  </do-if>  
  <do-strip-xpath expression="./driver-operation-data"/>  
 </actions>undefined</rule>  

Comments

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...

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 ...

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]" na...