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?

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

NETIQ IDM - Boost strap your start with identity application REST API

Boost strap your start with identity application REST API: If you want to play out with NetIQ rest API within identity application (IDMProv), you can see a few examples here: these are the rest API protected by Oauth2 Authorization (resource owner password credentials grant): The first step is to obtain token: ( you must have enabled client "rbpm" in the OSPF for the resource owner password credential grant) flow: An example is taken in c#: (postman) Get an access token: var client = new RestClient("https://<your host>/osp/a/idm/auth/oauth2/grant"); client.Timeout = -1; var request = new RestRequest(Method.POST); request.AddHeader("Content-Type", "application/x-www-form-urlencoded"); request.AddHeader("Authorization", "Basic Basic bas64 encoded string clientid<rbpm>:clientsecret>"); request.AddHeader("Content-Type", "application/x-www-form-urlencoded"); req