[ brummelhook public repository ] | |
---|---|
With the introduction of IDM 4 driver configs can now be imported as packages from repositories. I've already packaged
some of the drivers below and publish them via the Brummelhook Public repository. New stuff will most likely be added
there as well. To connect your Designer 4 installation to the Brummelhook Public repo, go to Window -> Preferences -> Novell -> Package Manager -> Online Updates and add the URL on the right to your list of Package Update URLs. |
Brummelhook Public repo at http://www.brummelhook.com/download/idm/packages/ |
[ password notification service driver ] | |
For quite a while, we used to run the
password expiration email notification cool tool, which helped reducing password-related helpdesk calls a lot.
Nevertheless, I never liked the fact that it runs outside the IDM environment and does not make use of the email
template features IDM provides, thus making it a bit complicated to maintain a consistent look and feel
throughout all email notifications. Luckily, though widely unknown, IDM supports time-triggered events that can be (mis)used to kick off custom actions: the publisher driver heartbeat. Add a schedule and a few policies that can read the clock, and there it is: an all-in-one IDM 2.x/3.x service driver for password notifications that can notify users, helpdesk and - still experimental - naudit on the following events:
Because IDM email templates are used, notifications can contain additional account data e.g. the time an intruder-locked account will be automatically unlocked again, or a company name for branding purposes. Email templates are maintained in iManager or Designer, making it easy to give them the same look and feel as the standard templates that come with IDM password synchronization. All versions up to 2.0.x require (and include) the java package bh-dirxmlutils.
|
download password notification service driver for IDM 2.x/3.0 (v1.1, .zip, 22kb)
download password notification service driver for IDM 3.5/3.6
import the password notification service driver packages (PWNotify*) for IDM 4.x from the
Brummelhook Public repo |
[ check_dxml_drvstate ] | |
Bash script to monitor Novell DirXML 1.1 and Identity Manager 2.x/3.x driver states from within Nagios or Icinga.
Usage:
check_dxml_drvstate [-s hostname|ip-address] -u username -p password -d driver-dn Basically a wrapper for "dxcmd -getstate". Leave out the -s option to check drivers running on the same machine as nrpe. |
download Nagios/Icinga plugin from MonitoringExchange
import the BH-NagiosMon driver add-on package for IDM 4.x from the
Brummelhook Public repo |
[ fsf/nsm user storage service driver ] | |
Loopback driver to automatically assign File System Factory/Novell Storage Manager policies to users.
An entitlement-enabled version for IDM 3.5 is also available. It uses RBE to determine the appropriate FSF/NSM policy for a user, making it a lot easier to implement complex assignment rules. |
download user storage service driver (v1.0, .zip, 7kb)
download user storage service driver with entitlements |
[ idm ad pwfilter.dll updater inf ] | |
The IDM AD driver requires a filter DLL to be installed on all DCs for password synchronization. Unfortunately, it seems as if the IDM 3.5 setup does not always update a previously installed version of pwfilter.dll (and associated files) properly. This INF installer can be used to update those files so they will be used after the next reboot. Many thanks to Alex McHugh for adding x64 support and fixing some bugs! Requires IDM AD driver |
download pwfilter.dll updater (v1.1, .zip, 2kb) |
[ com.brummelhook.dirxml.utils ] | |
Utility java classes for dirxml. Currently implements B64Converter to help accessing octet string attribute values .
Command line usage:
java -cp nxsl.jar;bh-dirxmlutils.jar com.brummelhook.dirxml.utils.B64Converter [-B64toHEX | -HEXtoB64 | -B64toTXT | -TXTtoB64 | -DecodeIntruderAddress] string1 [string2 string3...] Policy usage: 1. copy bh-dirxmlutils.jar to your dirxml/idm server, make sure it's in the class path 2. define a java name space in your policy, e.g. : <policy xmlns:bh-B64Conv = "www.novell.com/nxsl/java/com.brummelhook.dirxml.utils.B64Converter"/> 3. call the desired function from xpath, e.g.: <token-xpath expression="bh-B64Conv:B64toHEX($current-value)"/> |
download bh-dirxmlutils package (.zip, 4kb) |