Skip to main content

Novell IdM/DirXML : Deleting Publisher Event Cache on MAD (Microsoft Active Directory IdM driver)

Usually when you want to purge the event cache on the IdM driver, you usually put the driver state to disabled first and hitting it back to enabled state will work out. but that kills only the events which were waiting on the Subscriber ends... What about the purgeing events on the publiser end ????

My Scenario:

I was running a IDM 3.5.1 MAD driver between IDVault and Microsoft Active Directory, loading driver shim with Remote Loader on the other end. I wanted to purge events waiting on the publisher end.

the solution came out something like this:

a) on the dirver object there is an attribute called DirXML-DriverStorage. Delete it.

b) On the other end (where your remote loader is up and running). Delete the driver state file _DriverObjectDNAndDriverName>.xml.

c) Now start the Driver Engine and Remote Loader..
Labels:

Comments

Post a Comment

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...
2 comments
Read more

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 > ...
1 comment
Read more

NetIQ IDM - Trigger idm job from driver policy on driver startup with dynamic argument values

Looking at this article: https://www.netiq.com/communities/cool-solutions/how-start-idm-job-policy/ it shows you the complete recipe, except it does not show how to deal with dynamic argument values for the method itself; here is my version; I wanted to run this on the driver startup and wanted to let driver die if job execution did not succeed. 1. username must be "dotted" format; one can use parseDN; example: <token-parse-dn dest-dn-format="dot" src-dn-format="ldap">                         <token-local-variable name="local.sub.etp.resource.UserId"/>                     </token-parse-dn> 2. Jobname must be in "dotted" format too. 3. For more java lovers, one can dig into this: https://www.novell.com/documentation/developer/dirxml/dirxmlbk/api/com/novell/nds/dirxml/util/DxCommand.html ...
Post a Comment
Read more