Skip to main content

Posts

Showing posts with the label Novell Identity Manager

Digging IDMUnit - IdMUnit a must-have automated testing tool that integrates with Designer for Novell Identity Manager

Good news, The IDMUnit 2.0 is out ( http://www.idmunit.org/web/guest/idmunit20 )!.. and I just couldn't wait to try the tool and do some hands on with it. Now it comes with a documentaiton and a WebMinar which helps a lot to understand how it works and how it integerates with the Novell Designer. The Webminar is encoded with the "G2M3" encoding, so you need a decoder in order to see both video and audio. I downloaded it from the web : https://www2.gotomeeting.com/codec I started with installing the tool on my PC Windows Vista 32bit OS. I have the following setup: Novell Designer Version: 3.5, Build id: 20090916 Novell Identity Manager 3.6.1 Windows Server 2003 SP3 Novell eDirectory 8.8.x The first thing the IDMUnit documentation says to apply so called "Eclipse Overlay", i downloaded " Eclipse IDE for Java Developers (92 MB) " that from the URL " http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/galileo...

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...

Novell IdM 3.6 : Creating custom Subscriber PostProcessor Java extension for Delimited Text Driver Part 1

I had chance to write a custom PostProcessor extension for a Delimited Text Driver for Novell Identity Manager,  " t he PostProcessor extension should execute the code under another Windows Domain User account. So I decided to run the driver with Remote Loader Configuration, running the DirXML windows Service under another Windows Domain User Account. " Software and settings in my setup: * Novell Designer 3.0.1 (build  Jan 5, 2009) * Novell Identity Manager 3.6 / Windows Server 2003 R2 * Novell iManager 2.7.2 * Delimited Text Driver 3.6 ver 2.0 (imported configuration  file from Designer 3.0.1) * And the Delimited Text Driver was going to run on the remote server (Remote Loader),  * Java IDE was  (IntelliJIDEA) i started first with digging into documentation of the driver, and i came a cross this section: Using Java Interfaces to Customize File Processing: http://www.novell.com/documentation/idm36drivers/delimited/index.html?page=/documentation/idm36drivers/delimited/data/bkt...

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- n woType Just watch the last line, get this "n" out of the attribute name "DirXML-nwoType" to get the driver work!!!! Best of luck!

Novell IdM/DirXML : Determine direction of a Merge operation?

Recently, i was doing some stuff based on on the Merge operation on the Command Transformation ( Subscriber), but somehow those of my rules were being triggerd even if Merge operation was coming from (publisher).. and it was really bugging me a lot.. after spending few seconds, i figured out a maigc default Novell boolean local variable in the policy builder called 'fromNDS'!! so adding another condition to those of my rulles like this += if (fromNDS) = true saved me from writing my own java utility class..

Novell IdM/DirXML : Policy Builder and Local/GCVs

Comparing Local Variable value with GCVs in the Policy Builder... I had to comapre a value from the local variable with a value from a global variable.., so i was thinking how to to solve this?.. well after some search.. i solved it! Suppose you have a lcoal variable name called : lcl-myVariable and you want to compare the value of that local variable with a Global variable's value in the Policy Builder: so that would be: if lcl-myVariable = ~global-myVariable~ and same goes with the comparing local variable values with the local variables values if lcl-myVariable = $local-myVariable$ the second option might be creating a java String Utility Classes, which would be little overkill for this solution, i guess...