Platform / Sign-on & multi-factor
Sign-on & multi-factor
A full identity provider — not a login page bolted onto something else.
Case by case
Someone signs in from a new device, in a new country.
Risk rises, so proof is asked for again — a passkey, not another password prompt.
→ Phishing-resistant. No help-desk call.
A user opens the payments system mid-session.
The action is sensitive, so the check happens then — not when they happened to log in this morning.
→ Sensitivity drives it, not the clock.
Their password turns up in a breach dump.
Sessions cut, sign-in blocked, enrolment forced on next contact.
→ Minutes, not a Monday.
Under the hood
What you actually get
A full identity provider on both sides of every protocol — not a login page bolted on.
OIDC provider and client
Runs as a full OpenID Connect authorization server — discovery, JWKS, authorization-code with PKCE, refresh and scopes — and as a relying party to external OIDC providers.
SAML 2.0 IdP and SP
Issues signed assertions to downstream applications as an identity provider, and federates inbound to Okta or Entra ID as a service provider, with attribute mapping, auto-provisioning and single logout.
Every second factor
Passkeys and WebAuthn (platform biometrics and roaming keys), TOTP, email and SMS one-time codes, push approval, cross-device QR sign-in and backup codes.
Risk-based step-up
Impossible-travel and unknown-device signals score each sign-in and raise the proof required only when risk moves — assessed inline on every login, not on a fixed clock.
Live session defence
Session-hijack detection on location and device drift, and MFA-flood detection on sliding-window attempt counts, can burn a session family or auto-deny when armed.
Directory bind and discovery
Verifies passwords straight against an external LDAP or Active Directory, and routes users to the right provider by email domain through home-realm discovery.
Breach and reuse screening
Blocks sign-in and forces re-enrolment when a password appears in a breach corpus or matches a common-password list, with password-age checks at login.
Felt first by: IT operations and the IAM team. · Take this on its own — every edge speaks the standards your estate already speaks, so replacing it later stays cheap.