This document describes how to add IDM driver checking to an existing Zabbix monitoring solution. It does NOT describe how to deploy the Zabbix server itself, just the agents and the configuration of the items and triggers.
If you are using the IDM 4.0 SP2 Advanced Edition with additional toys like HPD, or if you are using IDM 4.5 AE with the same pieces, you may have the opportunity to use Mobile Approvals from an Android or other phone. This is basically a simplified mobile interface made to let those doing approvals…
How to use ndstrace to find out the number of successful and unsuccessful authentications.
Policy Types and Extensions There are different type of policies in NetIQ Access Manager, namely Authorization Policies, ID Injection Policies, Form Fill Policies, Role Assignment Policies and External Attributes Policies. The existing capabilities in Access Manager will suit for most of the general use cases. But sometimes it is necessary to write some custom code…
Customers routinely create custom scripts (Right clicks, Automations, Jobs, etc) to send out emails, bring up element/alarm data, open a helpdesk ticket, etc. While parts of the java script are NOC related, most of the scripting is around java. For instance, sending an email or adding a row to a database is a java exercise,…
This tool will help you validate that passwords have been set.
I am working towards implementing IDM 4 into my environment. I found that on one of my servers, the driver had stopped without my knowledge. So I decided to write a bash script to check the status of the driver, restart it if needed, and email whenever the status of the driver changes.
Updated: Since the release of eDirectory 8.8.0 support for multiple instances of eDirectory on a single box has been available. Using the ndsconfig and especially the newer ndsmanage tool configuring multiple instances of eDirectory is also very easy to do. One feature that has been missing since that time has been the ability to start/stop multiple instances as easily as one can start/stop the first root-based eDirectory instance of a root-installed eDirectory during startup/shutdown. The time has come to overcome that.
For a while now I have wanted to see how many controls eDirectory really could handle, even if they were not supported. It should be mentioned loudly and clearly that as of eDirectory 8.8.5 some of these controls work but THEY ARE NOT SUPPORTED so if they do not work properly submit a bug or an enhancement but don’t expect a quick response. Also for some of these there are definite limitations with how they work. I’ll try to cover those as I go.