Contact Aleksandar Mujadin
No author bio information
0 points earned on legacy (former) Cool Solutions site
1370 points earned on this site
The eDirectory 8.8 LDAP Server component supports a number of different trace levels that can be used to troubleshoot LDAP connections and queries. One can check the LDAP trace output using the ndstrace utility by enabling the +LDAP flag or by using DSTrace in iMonitor. The normal way to change the trace level is to…
This is a simple collector for the Linux daemon “dnsmasq”, a lightweight DHCP/DNS server. I developed it during a Sentinel course I attended (Sentinel Software Developer Kit: Building Collectors and Reports which I recommend). This is a development build, not a production build. As of now it only supports the DHCP part of dnsmasq. It handles…
The authentication process for the Reporting Module and all other Identity Applications has changed between IDM 4.0.x and IDM 4.5 so the old way of cleaning the Reporting database using REST won’t work anymore. Here are the updated instructions for IDM 4.5. Recently I performed some testing with about 1 million users and 40 000…
Recently I had a need to clean up both historic and current data from the Identity Reporting Module database (also known as the Identity Information Warehouse) and start with a fresh database. In Identity Manager v4.0.2 there is a pretty quick and painless way to do that without resorting to manual SQL scripts. It’s based on the REST…
Here are some notes I took during my attempt to install the Permission Collection and Reconciliation Service (PCRS) on a new AD driver at a client.
This article explains how you can use the NMAS HOTP login method together with the YubiKey hardware token from Yubico.
Updated: New in v2.7: Better feedback when handling drivers, new root DSE Viewer, ability to preview the results of a query in Associations Manager, support for anonymous binds, ability to export the eDirectory CA public key, support for ADLDS and Lotus Domino LDAP, ability to specify the base DN.
alekz explains how to create a password policy that uses the Generate Password token, but excludes some characters or numbers that could confuse users (where they might enter 1 instead of l, for example.) Very nifty!