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



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