Does Key2XS work with NetIQ Identity Manager or OpenText Identity Manager?

Both names refer to the same product. NetIQ Identity Manager became part of OpenText and is now marketed as OpenText Identity Manager. Key2XS connects to it regardless of which name your organization uses.

Does Key2XS replace OpenText Identity Manager or iLOQ?

No. Key2XS is middleware. Identity Manager remains the identity platform, iLOQ remains the locking system. Key2XS connects the two.

Does connecting iLOQ require changes to an existing Identity Manager architecture?

No. Key2XS connects through standard interfaces and does not require changes to drivers, the Identity Vault or existing integrations.

How long does an OpenText Identity Manager iLOQ integration take?

A standard integration is live in under two hours. Key2XS connects to Identity Manager and iLOQ through pre-built connectors, so no custom development is required.

Is the OpenText Identity Manager iLOQ integration suitable for NIS2 and CER compliance?

Yes. Both directives require governed, auditable control over physical access to premises. Key2XS provides the policy enforcement and audit trail that connects Identity Manager governance to physical keys.

OpenText NetIQ Identity Manager iLOQ Integration

Every system is connected to your Identity Vault. Except the keys.

Organizations running OpenText Identity Manager have often built their identity landscape around it for a decade or more. The event-driven engine keeps directories, HR systems and applications synchronized, and when something changes at the source, every connected system follows.

Physical keys are the exception. They are managed in a separate key administration, issued by a different department, and untouched by the events that govern everything else. In daily practice that means:

A leaver event that cleans up every connected system while their keys stay valid
Department transfers that update accounts and roles but not building access
Temporary staff whose contract end date exists in Identity Manager but not at the key cabinet
Physical access questions during audits that the identity team cannot answer from their own system

Under NIS2 and the CER Directive, critical entities must govern access to premises with the same rigor as access to information systems. An identity architecture that stops at the digital boundary leaves that requirement unmet.

Physical keys join your event-driven landscape

Key2XS is middleware that treats iLOQ like one more connected system. It reads identities and role and entitlement assignments from OpenText Identity Manager and orchestrates the corresponding key rights in iLOQ.

How it works

Connect. Key2XS connects to your OpenText Identity Manager environment and your iLOQ environment through their standard APIs. A standard integration is live in under two hours, with no changes to your existing drivers or Identity Vault.
Map. Roles and entitlements in Identity Manager are mapped to iLOQ key rights and lock groups. A role like “Ward Nurse - Location East” can correspond to exactly the wards, medicine rooms and storage spaces that role requires.
Orchestrate. When an assignment is created, changed or removed in Identity Manager, Key2XS applies the matching change to the person's iLOQ key rights in near real-time. The leaver event that disables accounts now also closes doors.
Prove. Every key right traces back to an identity, a role and a moment in time, in one tamper-evident audit trail.

What synchronizes between OpenText Identity Manager and iLOQ

From OpenText Identity Manager	To iLOQ via Key2XS
Identities (joiners, movers, leavers)	Key holders created, updated or deactivated
Role and entitlement assignments	Key rights and access to lock groups
Deactivations and contract end dates	Immediate withdrawal of key rights
Assignment history	Documented authorization behind every key

Changes flow through in near real-time, so a revocation in Identity Manager does not wait for a nightly batch to reach your keys.

Built for critical environments

Key2XS is used where physical access affects public safety, service continuity or regulatory compliance: utilities, government, transport, healthcare and industry.

NIS2 and CER ready. A continuous, tamper-evident audit trail links every physical access right to an identity and a policy decision.
Built for continuity. The Key2XS platform is engineered for 99.99% availability, matching the uptime expectations of critical infrastructure operations.
Security by design. All communication between Key2XS, Identity Manager and iLOQ is encrypted in transit with TLS 1.3, and data at rest is protected with AES-256.
Non-disruptive. Key2XS orchestrates access rights through the iLOQ management interface. Your locking plan, locks and keys remain untouched, and your Identity Manager architecture stays exactly as it is.

Why not build an iLOQ driver yourself?

The driver model in OpenText Identity Manager makes custom connections possible in principle. In practice, a homegrown bridge to a locking system means specialized development, an audit layer you must design yourself, and years of maintenance across upgrades on both sides. Key2XS delivers this as a maintained platform:

Live in under 2 hours. A standard OpenText Identity Manager to iLOQ integration is up and running in under two hours, not weeks or months
Maintained connectors that absorb API changes on both sides
Purpose-built audit and reporting for physical access governance
Certified by ASSA ABLOY for its locking system integrations, and a certified SailPoint Technology Alliance Partner on the IAM side
Support for additional IAM systems (SailPoint, Microsoft Entra ID, Okta, One Identity) and key systems (ASSA ABLOY eCLIQ and PROTEC) from the same platform, so your architecture is not locked to one vendor pairing

Connect OpenText Identity Manager to iLOQ