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

Post a Comment

Popular posts from this blog

Experience writing a Java based DirXML Driver

Based on the customer project, I wrote a DirXML driver which provision users through Novell Identity Manager 3.5.1 to their company intranet portal ( A Plone System). The portal exposed the RESTful API interfaces. So I started looking first at the Novell SOAP driver to see if it fit our needs. But while reading the driver documentation i felt it required too much XSLT knowledge + more customization and testing on the driver. And again it used the Apache HttpClient, Which is more a HttpClient rather then it targets to any specific protocol implementation. So If you could build SOAP messages at your own so it would help you in transporting these message back and forth between IDM and Application. The Novell SOAP driver comes up with two built in configurations "SPML and DSML", but in my case none of them were suitable. I had always wished to write my own DirXML driver at my own, so I thought why not just take this opportunity to fulfill my wish and at the same time get s...
1 comment
Read more

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

Novell IdM 3.6 : Creating custom Subscriber PostProcessor Java extension for Delimited Text Driver Part 1

I had chance to write a custom PostProcessor extension for a Delimited Text Driver for Novell Identity Manager,  " t he PostProcessor extension should execute the code under another Windows Domain User account. So I decided to run the driver with Remote Loader Configuration, running the DirXML windows Service under another Windows Domain User Account. " Software and settings in my setup: * Novell Designer 3.0.1 (build  Jan 5, 2009) * Novell Identity Manager 3.6 / Windows Server 2003 R2 * Novell iManager 2.7.2 * Delimited Text Driver 3.6 ver 2.0 (imported configuration  file from Designer 3.0.1) * And the Delimited Text Driver was going to run on the remote server (Remote Loader),  * Java IDE was  (IntelliJIDEA) i started first with digging into documentation of the driver, and i came a cross this section: Using Java Interfaces to Customize File Processing: http://www.novell.com/documentation/idm36drivers/delimited/index.html?page=/documentation/idm36drivers/delimited/data/bkt...
1 comment
Read more