Skip to main content

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.

The application will automatically set the user security context as the current logged on domain user ( Use current credentials). Or alternatively you can define credentials under which this application will run. I suggest to run this application under the same user which has been configured on the AD driver.

The application takes input from a driver state file "DRIVER_DN__state.xml", which can be found on the server, location(s) depends on the driver configuration setup (remote loader) or without remote loader. (Read the Novell IDM documentation for more details..)

And that's it!, Just click "Run", and you will see the events in a text file that can be opened either in notepad.exe or from within this application (View/Cache Log).

Terms of Use of Applications:

You understand and agree that you install and/or use all applications at your own risk.

downlaod location (coolsolutions)

http://www.novell.com/communities/node/9245/quick-dirty-ad-cache-inspector-ad-driver-novell-identity-manager



Comments

Popular posts from this blog

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

NetIQ IDM - SOAP driver -- Handling SOAP service response and manufacturing user association without XSLT

Always pain working with SOAP service and its handling of service response on Query(matching) for user to work with matching policies? Here is the quick wins; without reading  those long lengthy & boring useless SOAP driver blog series at netIQ forums; 1. Make sure you have mapped User class in the schema map with some service attributes 2. Make sure Input and Output policy is registered with all the namespaces you have in your request/response soap messages, example <policy xmlns:soap="http://www.w3.org/2003/05/soap-envelope" 3. I have added operation-data (which is being generated from the Output policy) as part of the SOAP query, but you can skip it if you do not need this. src-dn and association are important to indicate engine for building association.  Operation data will help you to identify operation type and you can carry actions according to it. Inject this on Output ( To support user matching) to send service request: < rule > ...

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