At Tongji University, the problem was what happened after somebody’s job changed. Its existing Sun Identity Manager setup lacked clear integration with personnel systems. When employees moved or left, the changes could not be synchronized with the relevant applications. The organization knew something the software did not. That is an uncomfortable arrangement for a security system.
- NetIQ connects identity records to accounts and permissions.
- Its customers include universities with sprawling IT estates.
- Now owned by OpenText, it spans lifecycle automation, sign-in and governance.
Tongji chose NetIQ Identity Manager and Access Manager. Connecting HR to account creation and disabling meant the personnel record could trigger the practical change. The university reported a 60% reduction in identity and access-related workload and a 30% saving in user administration costs. Those are customer-specific results in an OpenText case study, but the mechanism is refreshingly concrete.
The login that outlives the job
Enterprise identity management sounds like a department that needs a department. Its basic problem is familiar: one person appears in several systems, each maintaining its own version of who that person is. The trouble begins when those versions disagree. A departing employee is an especially useful test. Can every connected application learn that the relationship has ended?
NetIQ sells software for coordinating those answers. Today it sits in OpenText’s cybersecurity portfolio, serving organizations that must connect cloud services with directories and applications they still operate themselves. Its appeal is easiest to understand where replacing every old system is impractical. The business needs existing systems to agree about access while people keep working.
A weekend with 10,000 new accounts
The University of Westminster offers a second way to see the problem. Its historical NetIQ case study describes approximately 70,000 student accounts and 7,000 staff accounts across dozens of systems. These are account counts, not today’s enrollment figures. A relatively small IT team had to make that population usable.
The university connected eDirectory and Microsoft Active Directory through Identity Manager, establishing common credentials and automating account provisioning. Staff records and student records could initiate the process. At enrollment peaks, Dave Marriott, its EndPoint Systems team leader, described provisioning 10,000 accounts over one weekend. Doing the same administrative job repeatedly had become something a machine could handle.
“does exactly what it says on the tin”
Dave Marriott · University of Westminster
That plainspoken endorsement suits NetIQ. The impressive part happens behind the screen: a person enters one authoritative system, and the appropriate accounts follow. Shared credentials also spare users the ritual of becoming a slightly different person in every application.
Three questions behind one login
The product names require a little patience. Identity Manager handles the lifecycle: create accounts, update attributes, assign access and remove it. An Identity Vault holds identity information, while drivers move changes between connected systems. OpenText emphasizes an event-based architecture, so a change can initiate action instead of waiting for a human to repeat it elsewhere.
Access Manager handles entry. It supplies single sign-on and federation, supporting standards including SAML, OAuth and OpenID Connect, as well as services without federation support. Identity Governance asks whether access remains appropriate, using reviews, approvals and policy enforcement. Advanced Authentication adds multifactor and passwordless options. Privileged Access Manager addresses powerful accounts and controlled administrative sessions.
- 01A record changesJoin · move · leave
- 02Policy decidesRoles · rules · approvals
- 03Systems respondCreate · update · disable
This puts NetIQ across several buying decisions. SailPoint offers identity governance and provisioning; Okta offers lifecycle management and access products. There is overlap. NetIQ’s useful distinguishing detail is its combination of event-driven synchronization, directory integration and adjacent access controls. Buyers should test those mechanics against their actual applications rather than treat a portfolio diagram as proof of compatibility.
The name changed hands. The work stayed.
NetIQ began in 1995 with founders including Ching-Fa Hwang, its first president and CEO. Its original focus was systems management; a 2000 securities filing dates the first AppManager sales to February 1997. AppManager monitored application and infrastructure health, gathered performance information and supported responses to problems. Coordinating complicated estates was part of the business before identity became its defining subject.
AttachmateWRQ agreed to acquire NetIQ in 2006 for approximately $495 million. Micro Focus completed its merger with the Attachmate Group in 2014. OpenText acquired Micro Focus in January 2023. That last transaction’s roughly $5.8 billion price covered Micro Focus as a whole. It should never be mistaken for a NetIQ valuation.
The portfolio continues to change. OpenText announced its first full SaaS Privileged Access Manager release in March 2026, as an add-on to Core Identity Foundation. September 2026 release notes for Identity Manager’s 4.9 branch describe third-party component security updates. The two announcements show the parallel work of selling new deployment options and maintaining installed software.
The price of getting the details right
NetIQ’s 2014 Identity Manager 4.5 announcement advertised starting license pricing of $20 per user. That is a historical price for a particular release, far removed from a current project quote. The commercial model combines enterprise software with support and services; newer offerings also include SaaS. Connectors, deployment choices and implementation work affect what a customer actually buys.
The practical lesson from these deployments is to establish which record controls each change before automating it. Map the systems that must respond. Test a new hire, a transfer and a departure. Check the downstream account, including its removal. This is an inference from NetIQ’s architecture and the customer examples: reliable automation depends on reliable inputs and explicit rules.
Where personnel records arrive late, permissions lack owners or an application cannot be connected properly, software cannot supply the missing agreement. A simpler estate may need less machinery. NetIQ earns its place when coordinating identities across an untidy organization removes more work than maintaining the coordination creates.