Skip to main content

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"> <token-local-variable name="local.sub.ctp.Subscriptions" /> </arg-string> <arg-string name="IssueTicket"> <token-text xml:space="preserve">N/A</token-text> </arg-string> </do-start-workflow>


to catch the error use following condition with local variable  error.do-start-workflow


<do-if> <arg-conditions> <and> <if-local-variable mode="regex" name="error.do-start-workflow" op="equal">.+</if-local-variable> </and> </arg-conditions> <arg-actions> <do-trace-message level="3"> <arg-string> <token-text xml:space="preserve">Workflow Error Detected PLACEHOLDER</token-text> </arg-string> </do-trace-message> </arg-actions> <arg-actions /> </do-if>

Comments

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

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