Skip to main content

NetIQ IDM - IDM 4.0.2 AE VDX Webservice By Exmaples SOAP

Currently working on a project where  i need to integrate a 3rd party application with the  identity manager 4.0.2 AE through its exposed SOAP based webservices such as Resource, Role, Workflow and VDX.


Things to consider:

a)DAL entityKey
b)DAL attributeKey
c)DAL attribute search  flag ( if you want to query on a attribute).
d) Rights


VDX Webserivce SOAP by examples:

Query:

SOAP Request:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.novell.com/vdx/service">
   <soapenv:Header/>
   <soapenv:Body>
      <ser:queryRequest>
         <!--Optional:-->
         <!--type: string-->
         <ser:arg0>user</ser:arg0>
         <!--Optional:-->
         <ser:arg1>
            <!--Zero or more repetitions:-->
            <!--type: string-->
            <ser:string>FirstName</ser:string>
            <!--type: string-->
            <ser:string>Department</ser:string>
         </ser:arg1>
         <!--Optional:-->
         <!--type: string-->
         <ser:arg2>FirstName='Maqsood*' AND Department='*'</ser:arg2>
      </ser:queryRequest>
   </soapenv:Body>
</soapenv:Envelope>
SOAP Reply:


<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <SOAP-ENV:Body>
      <ns1:queryResponse xmlns="http://www.novell.com/vdx/service" xmlns:ns1="http://www.novell.com/vdx/service">
         <result>
            <entries>
               <entry>
                  <key>cn=maqsood,ou=idm,o=coolstuff</key>
                  <values>
                     <attribute>
                        <binaries/>
                        <booleans/>
                        <dates/>
                        <integers/>
                        <strings>
                           <string>Maqsood Ali</string>
                        </strings>
                        <type>String</type>
                     </attribute>
                     <attribute>
                        <binaries/>
                        <booleans/>
                        <dates/>
                        <integers/>
                        <strings>
                           <string>Back Office</string>
                        </strings>
                        <type>String</type>
                     </attribute>
                  </values>
               </entry>
            </entries>
         </result>
      </ns1:queryResponse>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>


GetAttribute

SOAP Request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://www.novell.com/vdx/service">
   <soapenv:Header/>
   <soapenv:Body>
      <ser:getAttributeRequest>
         <!--Optional:-->
         <!--type: string-->
         <ser:arg0>cn=maqsood,ou=idm,o=coolstuff</ser:arg0>
         <!--Optional:-->
         <!--type: string-->
         <ser:arg1>user</ser:arg1>
         <!--Optional:-->
         <!--type: string-->
         <ser:arg2>FirstName</ser:arg2>
      </ser:getAttributeRequest>
   </soapenv:Body>
</soapenv:Envelope>


SOAP Reply

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <SOAP-ENV:Body>
      <ns1:getAttributeResponse xmlns="http://www.novell.com/vdx/service" xmlns:ns1="http://www.novell.com/vdx/service">
         <result>
            <binaries/>
            <booleans/>
            <dates/>
            <integers/>
            <strings>
               <string>Maqsood Ali</string>
            </strings>
            <type>String</type>
         </result>
      </ns1:getAttributeResponse>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>



Comments

Dan A said…
Howdy,

I too am trying to integrate a third party app via VDX with the DAL.

I defined DirXML-Driver as an entity in DAL and CN as an attribute. However, during my testing on the web service the CN attribute is returnining null. Have you seen this?
August 15, 2013 at 12:13 PM
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

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...
2 comments
Read more