Skip to main content

NetIQ IDM - How to read String type data from Query nodeset done from command transformation



Suppose  query nodeset:

 <do-set-local-variable name="local.sub.etp.q.User" scope="policy">  

   <arg-node-set>  

    <token-query class-name="User" scope="entry">  

    <arg-match-attr name="CN">  

     <arg-value type="string">  

     <token-src-attr class-name="User" name="CN"/>  

     </arg-value>  

    </arg-match-attr>  

    </token-query>  

   </arg-node-set>  

   </do-set-local-variable>  



Output:



 <nds dtdversion="3.0">  
  <source>  
   <product build="20180222_0635" version="1.0.0.2">Identity Manager REST Driver</product>  
   <contact>NetIQ Corporation.</contact>  
  </source>  
  <output>  
   <status event-id="0" level="success" type="driver-general">  
    <operation-data prop.pub.itp.matached="true" prop.pub.itp.matached.target.DN=""/>  
   </status>  
   <instance class-name="users" event-id="0" src-dn="DC7F364B172747698A7685CE9CD705C3">  
    <association state="associated">DC7F364B172747698A7685CE9CD705C3</association>  
    <attr attr-name="Object Class">  
     <value value="string">users</value>  
    </attr>  
    <attr attr-name="name">  
     <value value="string">Dude</value>  
    </attr>  
    <attr attr-name="phone">  
     <value value="string">null</value>  
    </attr>  
    <attr attr-name="count">  
     <value value="string"/>  
    </attr>  
   </instance>  
  </output>  
 </nds>  


Reading phone info:

 <do-set-local-variable name="PhoneInfo" scope="policy">  
   <arg-string>  
    <token-xpath expression="$local.sub.etp.q.User/attr[@attr-name=&apos;phone&apos;]/value&#xd;&#xa;"/>  
   </arg-string>  
   </do-set-local-variable>  
   <do-trace-message>  
   <arg-string>  
    <token-text xml:space="preserve">GOT PHONE INFO => </token-text>  
    <token-local-variable name="PhoneInfo"/>  
   </arg-string>  
   </do-trace-message>  


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 - Start workflow from policy and catch error

Those who want to avoid slowness of designer UI, use XML editor for fast delivery of code by providing following xml stub for start workflow :-) < do-start-workflow id = "$local.sub.etp.resource.UserId$" time-out = "30000" url = "$local.sub.etp.resource.Endpoint$" workflow-id = "$workflow-ldap-dn$" > < arg-password > < token-local-variable name = "local.sub.etp.resource.Password" /> </ arg-password > < arg-dn > < token-local-variable name = "lv.user.ldap.DN" /> </ arg-dn > < arg-string name = "Product" > < token-local-variable name = "lv.group.ldap.DN" /> </ arg-string > < arg-string name = "Accounts" > < token-local-variable name = "lv.user.ldap.DN" /> </ arg-string > < arg-string name = "Subscriptions" > ...