Identity Management Success

Tracing all dependencies for a deliverable can make the difference between success and failure. In most organizations, perception is 9/10ths of the law.

General rule: Server side integration is relatively easy compared to mixed client and server side integration. For pure web and web service applications, all integration work can be conducted on the server, and you can get up and running quickly with your new IdMS.

However, if you have a client package - say Notes or Outlook - in your environment, ensure that your analysis has factored in all possible software versions and permutations. Each permutation may have its own file and configuration dependencies. While one version may integrate flawlessly with your IdMS system, another may not work at all, or generate unpredictable results. It is not enough to see your application version on the IdMS vendor’s compatibility list. Most vendors only count retail or “vanilla” versions and configurations.

Dependency Solution:

• Standardize clients before you integrate
• Ensure that all files within a given desktop package are organized by department and version.
• Use Group Policies in Active Directory, or Configuration Management tools in UNIX, to standardize group files and password lists
• Update desktop packages to include your latest internally supported versions
• Test updates for remote users and sites *first*

Following these guidelines can significantly reduce your risk of failure due to application incompatibilities and dependency failure.