NetIQ Identity Manager

From Wikipedia, the free encyclopedia
  (Redirected from Novell Identity Manager)
Jump to: navigation, search
NetIQ Identity Manager
Developer(s) NetIQ
Initial release July 24, 2000
Stable release 4.0.2 / June 22, 2012 (2012-06-22)
Operating system Cross-platform
Type Identity management
License Proprietary
Website https://www.netiq.com/products/identity-manager/advanced/

NetIQ Identity Manager (a.k.a. IDM) was formerly owned by Novell. IDM is NetIQ's implementation of Identity Management software. Previously known as DirXML the product utilizes XML-based configuration files to determine the product's implemented functions. With synchronization capabilities out of the box including various directories, databases, phone systems, operating systems, and HR systems, IDM strives to ease the administrative efforts of large enterprises by preventing administrative effort duplication. IDM 3.6.1 was released June 4, 2009.

Supported applications[edit]

IDM supports its own and a large number of third-party systems including the following: Novell eDirectory, Avaya, PeopleSoft, Oracle Database, SAP HR and User Management, Lotus Domino, Novell GroupWise, MySQL, any JDBC-compliant database, any LDAP-compliant directory, NIS, SIF, SOAP, Microsoft Active Directory, Microsoft Windows NT, RACF, ACF2 and many others including various Unix and Linux user databases.

For those supported systems drivers and configuration files have been pre-built and made ready for user customization. While a large number of systems are supported out of the box the possibility of integrating with other systems is there through customized drivers and configurations.

The current release of Identity Manager also provides integration with NetIQ's Security Information and Event Management (SIEM) product called NetIQ Sentinel. Among other things the integration lets Sentinel understand which of various users and roles are tied to a single person. This means that while a single person may have multiple usernames across various systems they can all be tied back to one individual because IDM sends the relevant relationships to Sentinel.

Documentation and Support[edit]

Documentation for IDM is available online at NetIQ's documentation website. Various online forums are also available for use on both NetIQ's and others' websites.

NetIQ offers traditional pay-per-issue support options or a consulting option to completely implement a new system.

Implementation and administration[edit]

There are a number of ways to develop, configure, or reconfigure an IDM implementation. Using NetIQ's own iManager has been an option since IDM 2. This option appeals to many administrators because it only requires a computer with a web browser and network access to perform all tasks associated with IDM. Because the configuration files are XML-based they can be imported and exported from anywhere in the world or edited directly in iManager's pages.

A newer method of administration, and especially, deployment, is now available through a product known as Designer. A free companion to IDM, Designer is written in Eclipse and runs on either a Linux or Windows workstation. Because it is a fat client it does not need to be connected to any networks to make changes to drivers though it does need to deploy changes for them to take effect. Designer is made to speed up the process of deploying new drivers and modifying and testing existing drivers by removing the multiple-click requirement that comes with any web interface, and offering quicker access to driver configuration settings. As of Designer 3.0, Designer also provides Subversion based version control. This simplifies development of an IDM implementation in a team environment, and also provides access to a history of changes made to IDM objects.

Along with changing and deploying entire environments Designer offers the added benefit of real-time testing of drivers before they are placed in production. An operation document can be fed into Designer and run through the driver's configuration and policies to see what will come out after the processing takes place. It is this output that would be used to make changes on either the eDirectory or application system. Because the test operation document is XML, just like the IDM configurations, the document can be easily viewed in a text editor or web browser before and after the simulation operation.

Further reading[edit]

External links[edit]