Repatriate Your Authentication

Why does your own login ask a stranger for permission?

The problem

Your employees prove who they are to your own systems by asking a third party to vouch for them — via OAuth? providers or Entra ID? . That party holds the credentials, the session state, and the kill-switch on your access. A complete read of its database contains every reusable credential your company has. Using external third parties to hold credential material and "validate" you to your own infrastructure is not reasonable, now that modern FIDO2? and passkey signing can be self-managed.

The mechanism

Passkeys? sign on each employee's own device: a private key sealed in secure hardware that never leaves it; the server holds only the public half. Nothing to phish, nothing to steal from a server-side database, nothing to reset through a help desk.

Self-hosting the signing is the step most organizations never take. LocalWebAuthn? — ours, open source — supplies the whole lifecycle between the WebAuthn ceremonies and a logged-in user: enrollment, credentials, challenges, sessions, revocation. It keeps no passwords, no password hashes, no TOTP seeds, no recovery codes. A complete read of its database contains no reusable authentication credential.

The transition

You don't flip a switch. KeyCloak? , an open-source identity broker, sits in the middle while your applications move over one at a time: it speaks the old protocols to the applications that still need them, while new and migrated applications go passkey-native. Repatriation without a flag-day — the third party becomes a chapter in the migration plan, not a permanent tenant in your infrastructure.

What an engagement looks like

  1. Assessment: inventory every application and identity flow; find what actually needs a third party and what doesn't.
  2. Design: the passkey architecture, the KeyCloak bridge, and the rollback plan.
  3. Migration: application by application, with parallel run where needed.
  4. Training: your administrators learn to run their own identity, not rent it.

FAQ

Q: Do we need to rip out Entra ID on day one? No. KeyCloak bridges the transition; applications move one at a time.

Q: Is self-hosted authentication safe? The server stores only public keys — a complete read of its database contains no reusable credential. That removes the credential database as a target.

Q: What about the devices? Passkeys work on every modern laptop and phone; enrollment is a few taps. Recovery is a policy, not a password reset.