authentik passkeys and WebAuthn
Rolling out passkeys and FIDO2 security keys in authentik: enrollment stage settings, user verification, discoverable credentials for passwordless login, passkey autofill, and restricting allowed authenticator models.

Pages on authentik capabilities buyers evaluate separately from basic SSO: passkeys and remote access.
Rolling out passkeys and FIDO2 security keys in authentik: enrollment stage settings, user verification, discoverable credentials for passwordless login, passkey autofill, and restricting allowed authenticator models.
Giving users browser-based RDP, SSH and VNC access to internal machines through the authentik RAC provider and outpost: endpoints, per-endpoint policies, session expiry and where it fits against a VPN or bastion.
Letting users request time-limited access to applications or entitlements with approvals in authentik 2026.8: request rules, reviewer groups and minimum counts, expiry, revocation and the audit trail.
Cutting off a compromised account in one action: what Account Lockdown deactivates and revokes, admin and self-service triggers, the packaged blueprint, and how it fits an incident response runbook.
Scheduling periodic reviews of applications, groups and roles for audits: lifecycle rules per object or type, reviewers and minimum counts, overdue tracking and the preview status of the feature.
Deactivating or deleting leavers on a set date with session and token revocation: scheduling from HR dates, review and cancellation, retries and event log evidence for joiner, mover and leaver controls.
Sending security events such as logouts, revoked sessions, MFA device changes and credential changes to subscribed applications with SSF: the backchannel provider model, Apple Business Manager, signing keys and event retention.
Serving WS-Federation relying parties such as SharePoint from authentik: the Enterprise requirement, SAML2 token type only, passive browser sign-in, and replacing AD FS for these applications.
Using the authentik Agent for SSH to Linux hosts, local device login and kubectl or AWS CLI authentication with authentik credentials: Enterprise and preview status, platform support and when to wait.
Allowing access only from compliant devices: the Fleet connector with an mTLS stage, the Chrome Enterprise Device Trust connector, device facts in expression policies, and Enterprise licensing.
Authenticating or enrolling users with client certificates from devices, smart cards, PIV cards or hardware tokens through the Mutual TLS stage: Enterprise licensing, CA trust and reverse proxy certificate forwarding.
Letting services act on a user's behalf without sharing the original token: token exchange and on-behalf-of in authentik 2026.8, trusted providers and sources, grant type settings, and key-bound ID tokens.
Ending sessions across applications when a user signs out: back-channel and front-channel logout for SAML, front-channel and back-channel logout for OIDC, post-logout redirect URIs and testing with real apps.
Giving scripts and AI agents delegated API access tied to a real user in authentik 2026.8: inherited policy access, expiry rules, API management and audit events, compared with plain service accounts.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.