 |
|
 |
|
 |
|||
 |
|||
|
|
Identity Management Study Business situation An international automation manufacturer has an implementation of the Sun Java Identity Manager product. The initial implementation was performed in June of 2005. The system serves a user community of 10,000 employees and contractors across North America, EMEA (Europe, Middle East, Africa), and Asia Pacific campuses. Its purpose is to provide security access workflows to manage user access across eight applications, which include, Active Directory, Lotus Notes, GEAC, Passport, and several custom applications. A number of stability and performance issues arose shortly after the implementation that could not be resolved by the implementation service provider and the company's own resources. Users were typically waiting for several minutes to provision a single application and there were regular system hang events, which would require a complete system shutdown and restart to resolve. The system was considered too unstable and underperforming to be considered a real utility for the company to realize value. As a result the company withdrew plans to expand the original system to support additional communities of users, resources, and workflows, including implementation of SAP users across international boundaries. And worse, the company's team did not have any internal knowledge of how the system worked, because the original services provider didn't involve the company in the development of the original system. The new improved system went live in July 2006 without incident. User provisioning workflows that used to take minutes are now being done in seconds. Plans are underway for system expansion to onboard additional systems including the company's SAPTM implementation. Prior to the redeployment and upgrade, the company's team believed the problems were caused by an inferior product. Laurus' expert services guided the team to understand that their problems were caused by a misguided implementation. The company's team is now "happy to own the solution". Technical situation The company was using an older version of Sun Identity Manager that has since been updated. Other performance issues were due to custom adapters that were written improperly. Workflows include:
Resources:
Solution Laurus Technologies was brought in to evaluate the stability and performance issues, and recommended an upgrade and redeployment of the EnterNow system to Identity Manager version 5.5. Laurus' expert services provided technical leadership, reverse engineering of workflows, best practices, QA, go live strategy, and mentoring to guide the company's team to reviving original system. The engagement lasted 12 weeks in duration and the new improved system went live in July, ahead of schedule, without any negative impact. Benefits
|
|
|
||||||||||||||||||
