Does Key2XS replace Okta or iLOQ?

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

Do Okta group rules work with Key2XS key management?

Yes. Key2XS reads group memberships from Okta regardless of how they are populated. If a group rule adds a user to a mapped group, the corresponding iLOQ key rights follow automatically.

What happens to physical keys when a user is deactivated in Okta?

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 an Okta iLOQ integration take?

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

Is the Okta 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 the Okta lifecycle to physical keys.

Okta iLOQ Integration | Key2XS Physical Access Governance

Every app is behind Okta. The building is not.

Organizations choose Okta to make identity the control point: one dashboard, one lifecycle, one place where onboarding grants everything and offboarding removes everything. That promise holds for hundreds of applications.

Physical keys break it. They are handed out at a desk, registered in a separate key management tool or a spreadsheet, and returned whenever someone remembers. So while Okta deactivation strips a leaver of every application in seconds, their key keeps working:

Offboarding flows that end at software, leaving doors open
Maintenance contractors whose Okta access expired but whose keys did not
No connection between a person's Okta profile and the keys they hold
Physical access audits assembled by hand, location by location

Under NIS2 and the CER Directive, critical entities are expected to govern access to premises with the same discipline as access to systems. The gap between Okta and your keys is precisely where that expectation bites.

Okta groups in, iLOQ key rights out

Key2XS is middleware that makes physical access one more thing Okta assigns. It reads users, groups and lifecycle states from Okta and orchestrates the matching key rights in iLOQ.

How it works

Connect. Key2XS connects to your Okta org and your iLOQ environment through their standard APIs. A standard integration is live in under two hours, with no custom development.
Map. Okta groups are mapped to iLOQ key rights and lock groups. A group like “Maintenance - Depot North” can correspond to exactly the depots, cabinets and technical spaces those crews need, and nothing else.
Orchestrate. When a user enters or leaves a mapped group, or is deactivated in Okta, Key2XS applies the change to their iLOQ key rights in near real-time. If your groups are populated by Okta group rules, physical access follows those rules automatically.
Prove. Every key right traces back to an Okta identity, a group and a moment in time, in one tamper-evident audit trail.

What synchronizes between Okta and iLOQ

From Okta	To iLOQ via Key2XS
Users (joiners, movers, leavers)	Key holders created, updated or deactivated
Group memberships	Key rights and access to lock groups
Deactivation and suspension	Immediate withdrawal of key rights
Assignment history	Documented authorization behind every key

Changes flow through in near real-time, so deactivating a user in Okta 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, Okta 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 script this with the Okta API?

Okta has excellent APIs and automation hooks, and iLOQ has an API too. But a homegrown bridge means owning connector code against two evolving platforms, building your own audit layer, covering every lifecycle edge case, and maintaining it for years while it quietly becomes critical infrastructure. Key2XS delivers this as a maintained platform:

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

Extend Okta to your physical keys