Skip to main content

Novell IDM 3.6 Work Order driver

Schema/Attribute name confusion in the default WO driver configuration file.

Identity Manager 3.6
Windows Server 2003 R2


Before starting with the driver,. please goto the Creation policy (Subscriber) and fix the name of the attribute:


do-veto-if-op-attr-not-available name=DirXML-nwoSendToPublisher
do-veto-if-op-attr-not-available name=DirXML-nwoStatus
do-veto-if-op-attr-not-available name=DirXML-nwoDoItNowFlag
do-veto-if-op-attr-not-available name=DirXML-nwoContent
do-veto-if-op-attr-not-available name=DirXML-nwoType




Just watch the last line, get this "n" out of the attribute name "DirXML-nwoType" to get the driver work!!!!

Best of luck!
Labels:

Comments

Post a Comment

Popular posts from this blog

Experience writing a Java based DirXML Driver

Based on the customer project, I wrote a DirXML driver which provision users through Novell Identity Manager 3.5.1 to their company intranet portal ( A Plone System). The portal exposed the RESTful API interfaces. So I started looking first at the Novell SOAP driver to see if it fit our needs. But while reading the driver documentation i felt it required too much XSLT knowledge + more customization and testing on the driver. And again it used the Apache HttpClient, Which is more a HttpClient rather then it targets to any specific protocol implementation. So If you could build SOAP messages at your own so it would help you in transporting these message back and forth between IDM and Application. The Novell SOAP driver comes up with two built in configurations "SPML and DSML", but in my case none of them were suitable. I had always wished to write my own DirXML driver at my own, so I thought why not just take this opportunity to fulfill my wish and at the same time get s...
1 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