Does Key2XS replace One Identity Manager or iLOQ?

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

Can iLOQ key access follow One Identity Manager approval workflows?

Yes. Key2XS acts on the assignments that exist in One Identity Manager. If a role or entitlement is granted through the request and approval process, the mapped iLOQ key rights follow that assignment automatically.

What happens to physical keys when an employee is deprovisioned in One Identity Manager?

Key2XS withdraws the person's iLOQ key rights in near real-time as part of the same flow. Physical and digital access are revoked together, and the revocation is logged.

How long does a One Identity Manager iLOQ integration take?

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

Is the One 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 One Identity Manager governance to physical keys.

One Identity Manager iLOQ Integration

Mature identity governance, ungoverned keys

Organizations running One Identity Manager tend to take governance seriously. Access is modeled in business roles, requests pass through approval workflows, and assignments are periodically attested. Auditors get answers from the system, not from memory.

Physical keys usually live outside that model. They are issued at a service desk, tracked in a separate application or a spreadsheet, and disconnected from the role model that governs everything else. The consequences are familiar:

Key possession that no longer matches anyone's current role
Leavers processed perfectly in One Identity Manager while their keys stay active
Approval and attestation discipline for applications, but not for doors
Physical access evidence assembled manually every audit cycle

For critical entities under NIS2 and the CER Directive, physical access to premises is explicitly in scope. A governance model that ends at the login screen leaves exactly the gap those directives target.

Keys as a governed entitlement

Key2XS is middleware that makes iLOQ key rights behave like any other entitlement in One Identity Manager: derived from roles, driven by lifecycle events, and always traceable to a decision.

How it works

Connect. Key2XS connects to your One Identity Manager environment and your iLOQ environment through their standard APIs. A standard integration is live in under two hours, with no custom development.
Map. Roles and entitlements in One Identity Manager are mapped to iLOQ key rights and lock groups. A business role like “Plant Engineer - Site South” can correspond to exactly the production halls, switch rooms and perimeter gates that role requires.
Orchestrate. When an assignment is created, changed or removed in One Identity Manager, whether directly or through your request and approval workflows, Key2XS applies the matching change to the person's iLOQ key rights in near real-time. Deprovisioning a leaver withdraws their physical access in the same movement.
Prove. Every key right traces back to an identity, a role and a decision, in one tamper-evident audit trail. Because key rights follow your roles, recertifying a role also recertifies the physical access it grants.

What synchronizes between One Identity Manager and iLOQ

From One 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
Deprovisioning and expirations	Immediate withdrawal of key rights
Approval decisions	Documented authorization behind every key

Changes flow through in near real-time, so a revocation in One 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, One 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.

Why not extend One Identity Manager yourself?

One Identity Manager is famously extensible, and building a custom connector toward iLOQ is conceivable. It is also a multi-month project that must be maintained across upgrades on both sides, hardened for edge cases in the leaver flow, and equipped with its own audit layer. Key2XS delivers this as a maintained platform:

Live in under 2 hours. A standard One 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, OpenText) and key systems (ASSA ABLOY eCLIQ and PROTEC) from the same platform, so your architecture is not locked to one vendor pairing

Govern iLOQ keys with One Identity Manager