authentik and FortiGate SSL VPN SAML integration
Authenticating FortiGate SSL VPN users against authentik with SAML: the SAML application, importing the signing certificate, the SAML SSO server and user group, and mapping groups to VPN portals.

Using authentik to authenticate VPN users, firewall administrators, mesh networks and Wi-Fi clients over SAML, OIDC, LDAP or RADIUS, with MFA where the protocol allows it.
Authenticating FortiGate SSL VPN users against authentik with SAML: the SAML application, importing the signing certificate, the SAML SSO server and user group, and mapping groups to VPN portals.
Signing firewall administrators in to the FortiGate management interface through authentik with SAML, separate from VPN users, with MFA and admin profiles mapped from groups.
Authenticating GlobalProtect VPN users with authentik over SAML: the SAML identity provider profile, authentication profile on portal and gateway, and group-based access.
Using authentik for SAML sign-in to the Palo Alto Networks next-generation firewall web interface: admin roles from attributes and keeping a local emergency admin.
Configuring SAML single sign-on from authentik to Cisco Secure Firewall Management Center for administrators, with role mapping and MFA.
Authenticating pfSense administrators and VPN users against authentik through an LDAP outpost: the LDAP provider and service account, search base, groups and code-based MFA in the bind password.
Using authentik's LDAP outpost as the authentication server for OPNsense administrators and VPN users: provider settings, bind account, group mapping and TLS.
Using authentik as a custom OIDC identity provider for a Tailscale tailnet: the WebFinger endpoint Tailscale requires on your domain, the OIDC provider settings and moving users from another IdP.
Signing users in to a self-hosted Headscale control server with authentik over OIDC: Headscale OIDC settings, allowed groups and domains, and node registration through the browser.
Using authentik as the identity provider for self-hosted NetBird: OIDC and device authorization settings, the management API service account, and group sync for access policies.
Authenticating Wi-Fi and wired 802.1X clients with authentik's RADIUS outpost and EAP-TLS: the Enterprise requirement, a private CA instead of a public one, the mutual TLS stage flow and certificate rollout to devices.
Adding MFA to VPNs and network devices that only speak RADIUS: PAP-only password authentication, appending TOTP, Duo or static codes to the password, why SMS codes cannot work, and when SAML on the VPN is better.

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.