Problem

A Forum reader recently asked:

“I need to know be able to effectively compare Novell IDM to Microsoft MIIS. My company wants to move to MIIS, and I want to prevent that.”

And here’s the response from Johan Akerstrom …

Solution

Here are few quick notes for you …

  • IDM has support for more drivers.
  • IDM has built in support for manual workflows (UserApp).
  • IDM has built in support for Flexible strong passwords.
  • IDM has GINA/Web-based Password Reset Management.
  • IDM uses a graphical designer for building business rules but can call external Java/ECMAScript code if necessary (it won’t need to often).
  • IDM has support for Role based entitlements.
  • IDM has auditing built in.
  • IDM is event-based.
  • MIIS rules needs to be coded in C# or VB.NET, except for very basic mappings. More or less, everything needs to be coded in MIIS.
  • MIIS has no gina password reset management.
  • MIIS is state-based.
  • MIIS Management Agents (equivalent of IDM Connectors) need to be scheduled for export, import and synchronization runs.
  • MIIS has no concept of roles or entitlements.
  • MIIS has no built-in auditing.
  • MIIS code can be debugged easily with Visual Studio.
  • MIIS is cheaper (there just might be a reason for that, though).
0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

No Comments
Jul 18, 2007
8:55 am
Reads:
887
Score:
Unrated