I was recently working on an Active Directory Driver for Novell IDM 4.0.1 in which most groups required an approval. Typically, this is not a difficult task as users would be able to make a request for a group which would start a workflow with an approval action within the workflow.
Recently, I customized an i5/OS connector to an AS/400 system. This was a system that I had limited experience with in the past, so the first step was researching what made a user within the system, what objects get attached to that user, and what permissions needed to be set for the user to have access to the subsystems they need. In doing that, I was able to gain a generic understanding of the OS/400 server, some basic commands, and how to traverse myself through the applications.
Testing is a tedious task that is necessary for almost every project in development. We use testing to ensure that the code written is functioning as intended and meets all the requirements requested by the customer. Normally, testing of identity management (IDM) drivers involves making events occur manually that the driver should be able to handle. We review the trace/log files created after each event and check the applications end results, to ensure everything is working correctly.
Researching ForgeRock OpenIDM 2.0, and the website’s claim to being flexible and easy to use, has sparked my interest into what the product has to offer. ForgeRock is growing in popularity in the development community because of its open availability and the user community forums. Developers are working together to help improve the software and make a strong code base. OpenIDM 2.0 is designed to help provide businesses with a solution for business process handling and compliance and the product excels at this by using JSON for reconciliation, synchronization, and mapping, making the process of bulk importing users into a system more developer/administrator friendly.
Recent Comments