NetIQ federation depth
SAML 2.0, OAuth 2.0, OIDC, WS-Federation and the older federation protocols NetIQ customers in regulated sectors still depend on. Cloud-native IAM often skips the long tail.
OpenText • Identity and access management
OpenText NetIQ Access Manager (formerly OpenText Access Manager) delivers SSO, federation, web access management, and modern authentication for regulated and on-prem-heavy enterprises that have not migrated workforce identity to cloud-only options.
OpenText NetIQ Access Manager gives regulated workforces one federation layer for SAML, OAuth, OIDC and older protocols such as WS-Federation and Kerberos, on-prem or hybrid, with Identity Manager feeding provisioning into its access policy.
What it is
OpenText NetIQ Access Manager is the federation and web access management product in the OpenText identity line. Banks, government agencies, defense contractors and hospitals have run NetIQ for workforce identity for two decades. Access Manager covers SSO, federation (SAML, OAuth, OIDC), web access management, and modern authentication. The 2026 return of the NetIQ name changed the label on the product, not the federation engine underneath.
Federation depth is the historical strength. Access Manager supports SAML 2.0, OAuth 2.0, OpenID Connect, WS-Federation, and a long tail of federation protocols regulated environments still use. Programs running heterogeneous SSO landscapes (legacy SAML providers alongside modern OIDC, SOAP-shaped web services alongside REST APIs) get one federation layer that handles all of them. Cloud-native IAM products often skip the long-tail protocols and force the program to migrate every consumer.
On-prem and hybrid operational shape is the second strength. Programs subject to data sovereignty, regulated workforce identity, or air-gap constraints run Access Manager on-premises while consuming cloud SSO as needed for SaaS apps. Cloud-only IAM (Okta, Microsoft Entra) is competitive on cloud-native programs but does not always fit regulated environments. Programs picking Access Manager are usually picking the regulated and on-prem operational shape, not generic SSO.
Access Manager programs stall when the platform is bought as a drop-in SSO replacement. Access Manager is operationally substantial. Federation policy, integration with NetIQ Identity Manager for provisioning, integration with Privileged Access Manager for elevated access, and on-prem operational discipline all require sustained investment. Programs that adopt Access Manager without operational discipline find the platform underused. Merito's engagement designs the operating model alongside the deployment, and Managed Services run it long-term for programs that want OpenText engineering without internal headcount.
Ideal use cases
What it is best at
SAML 2.0, OAuth 2.0, OIDC, WS-Federation and the older federation protocols NetIQ customers in regulated sectors still depend on. Cloud-native IAM often skips the long tail.
Programs subject to data sovereignty, regulated workforce identity, or air-gap constraints get an IAM that fits. Cloud-only IAM is not always an option.
Provisioning from Identity Manager flows into Access Manager federation policy. Programs running both get coordinated identity and access.
Passwordless and FIDO2 support paired with Advanced Authentication for risk-based MFA across workforce, customer, and privileged users.
FedRAMP-aligned editions where applicable, FIPS 140-2/3 cryptographic modules, audit-ready evidence for regulated workforce identity mandates.
Core capabilities
Where Access Manager does the work across heterogeneous identity protocols.
SAML 2.0 federation
SAML 2.0 IdP and SP roles for workforce SSO across SaaS and internal applications.
OAuth 2.0 and OIDC
OAuth 2.0 authorization server and OpenID Connect provider for modern API and SaaS integration.
Long-tail federation protocols
WS-Federation, WS-Trust, Kerberos, and legacy federation protocols regulated programs still use.
Web access management
Web reverse-proxy and policy-driven web access management for legacy applications.
Passwordless and risk-based authentication on regulated workforce.
FIDO2 and passwordless
FIDO2 webauthn and passwordless authentication for workforce SSO.
Advanced Authentication integration
Native pairing with OpenText NetIQ Advanced Authentication for risk-based MFA and adaptive authentication.
Step-up authentication
Risk-based step-up authentication on sensitive operations.
Access Manager inside the OpenText IAM line.
Identity Manager integration
NetIQ Identity Manager provisioning flows into Access Manager federation policy.
Privileged Access Manager pairing
Privileged identity flows through Access Manager for SSO into PAM-managed elevated sessions.
Identity Governance integration
Access reviews and SOD enforcement applied to Access Manager-managed entitlements.
Compliance reporting
Audit logs of sign-on and federation events, kept as evidence for SOX, HIPAA and PCI DSS reviews of workforce access.
Where it fits in the stack
Deployment and implementation
Licensing and packaging
Access Manager on-prem
On-prem deployment for regulated and sovereign workforce identity.
Best for: Regulated programs that cannot adopt cloud-only IAM.
Access Manager hybrid
On-prem with cloud federation extensions for SaaS apps.
Best for: Programs running mixed cloud and on-prem workforce identity.
Access Manager Government Cloud
FedRAMP-aligned editions for federal and government workforce identity.
Best for: Federal programs requiring FedRAMP-aligned IAM.
Merito services
Pick the engagement that matches where you are in the lifecycle.
Infrastructure design, deployment, federation policy, OpenText IAM line integration, operating-model design.
Explore serviceNetIQ Access Manager version upgrades and modernization path to NetIQ Identity Foundation where applicable.
Explore serviceIAM program scoping for Access Manager alongside Okta, Microsoft Entra, PingFederate, and ForgeRock.
Explore serviceApplication SSO integration, federation policy authoring, and identity-pipeline design.
Explore serviceNamed engineer, priority SLAs, and release-time coverage for Access Manager.
Explore serviceDay-to-day operation of Access Manager servers, federation policy changes and upgrades, for teams without in-house NetIQ engineers.
Explore serviceAccess Manager fundamentals, federation policy workshops and passwordless authentication design for identity architects and IAM operators.
Explore serviceIdentity engineers who know SAML, OIDC and NetIQ federation policy, placed on your team for long Access Manager rollouts.
Explore serviceOpenText NetIQ Access Manager licensing
Access Manager pricing arrives with infrastructure design, federation policy, OpenText IAM line integration, and operating-model design that turn 20 years of NetIQ workforce-identity depth into a sustained capability rather than a static deployment.
Merito point of view
Some IAM modernizations Merito has scoped ended with Okta or Microsoft Entra, which suits cloud-native enterprises with modern application landscapes. Others stayed on NetIQ Access Manager because of data sovereignty, on-prem operating constraints or air-gap requirements. Programs picking OpenText NetIQ Access Manager are usually picking the regulated and on-prem operational shape, not generic SSO.
Programs that already run NetIQ, are upgrading an older NetIQ Access Manager release, or face regulation that rules out cloud-only IAM should start with Access Manager. Greenfield cloud-native programs are usually better served by Okta. A team with a working PingFederate or ForgeRock deployment rarely gains enough from switching to justify the migration. Those options sit side by side in the scoping notes.
Cross-product OpenText IAM line integration is the platform claim that pays back when the program runs the full line. Identity Manager for provisioning, Access Manager for SSO and federation, Privileged Access Manager for elevated access, Identity Governance for access reviews, Advanced Authentication for MFA. Programs running standalone Access Manager get SSO; programs running it inside the line get coordinated identity operations.
What buyers usually underestimate
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Tell us which applications need SSO, which federation protocols they use, and any rules on where identity data must stay. A Merito OpenText specialist follows up within one business day.
NetIQ federation depth
SAML, OAuth, OIDC, WS-Federation, Kerberos, WS-Trust. Cloud-native IAM often skips the long tail.
Regulated and on-prem
On-prem and hybrid IAM for sovereign-cloud, air-gapped, and regulated workforce identity.
Next step
A Merito Access Manager engagement scopes federation policy, IAM line integration, and operating model. Programs that upgrade in place without a modernization plan leave value on the table.