BMC has killed its .Net Identity Management product suite in part because partner Microsoft is squeezing BMC out with development of its own identity software, according to an internal Microsoft memo.
BMC in early May quietly ended investment and development in the .Net Identity Management suite with the current version 5.2 being the final edition. Planned enhancements, such as support for the Service Provisioning Markup Language, have also been killed.
The details were revealed in a memo Microsoft sent last week to an internal email distribution list.
BMC .Net Identity Management is a suite of identity management tools, such as access control, provisioning, workflow, single sign-on and user self-service, that run on top of Microsoft’s Identity Lifecycle Manager (ILM) 2007 (formerly called Microsoft Identity Information Server).
The memo highlights a growing rift between Microsoft and its partners that develop identity management software for the Windows platform. Like BMC, Omada’s identity software requires the use of ILM, while Quest and NetPro list ILM as a platform option.
BMC has a similar Java-based identity management suite it will continue to sell in competition against Microsoft and others such as IBM.
The rift centres on ILM 2007, which is expanding to offer similar tools to BMC and others. It is ILM, which offers synchronisation, provisioning and management tools, that led BMC to kill is Windows-based identity platform, according to the memo.
The memo also cited features such as password management, password synchronisation and self-service coming in ILM 2.0, slated to go into beta in mid-2007, that contributed to BMC’s decision.