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

Post a Comment

Popular posts from this blog

My own developed - Active Directory Cache Inspector for AD Driver Novell Identity manager

Sometimes there is a need for us (Consultants) to see a snapshot of all the changes that happened on the Active directory side while the Novell AD IDM driver was stopped or was not running, before we decide to start the AD driver. Since Novell Identity Manager currently allows us to see all the events which happened in the Identity vault only, but not on the AD side, I decided to write such a tool myself, and of course wanted to share this tool with the consultants/community out there. It's a .NET 2.0 WinForm application, written in C# programming language. To run this tool you should have at minimum: .NET 2.0 framework installed, ( Not supported on the Linux platforms yet) This application must be run under the same user which is configured on the AD driver. Short Tutorial (How To): When you run the application (ADCView.exe), the application automatically discovers the current domain, a domain controller, and default domain naming context in the user logged in domain automatically
Post a Comment
Read more

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

Suppose query: <do-set-local-variable name="local.sub.ctp.QueryContacts" scope="policy"> <arg-node-set> <token-query class-name="User" scope="entry"> <arg-match-attr name="UPN"> <arg-value type="string"> <token-src-attr class-name="User" name="UPN"/> </arg-value> </arg-match-attr> <arg-match-attr name="contacts"> <arg-value type="string"> <token-text xml:space="preserve">get-contacts</token-text> </arg-value> </arg-match-attr> <arg-match-attr name="userid"> <arg-value type="string"> <token-association/> </arg-value> </arg-match-attr> </token-query> </arg-node-set> </do-set-local-variable> Outpu
Post a Comment
Read more