Required for the site to work (login, preferences, security). Always on.
Authentik: a hardening checklist for self-hosted identity providers
Authentik is an open-source identity provider for OIDC, SAML, LDAP and RADIUS. For MSPs running it themselves, a few hardening steps matter more than any single feature.
Authentik (goauthentik/authentik) is an open-source identity provider built for self-hosting, supporting OIDC/OAuth2, SAML, LDAP and RADIUS from a single Django-based backend. It's positioned by its maintainers as a replacement for commercial identity providers such as Okta, Auth0 or Entra ID for teams that want to run their own SSO layer rather than rent one. For MSPs, that trade brings real control — and real operational responsibility.

What running your own IdP changes
A hosted identity provider takes care of its own uptime, patching and break-glass recovery. A self-hosted one puts all of that on the MSP. Authentik decomposes into a handful of cooperating services — a Django/Python server handling OAuth2, OIDC and SAML flows, plus the admin interface and API — which is straightforward to run in Docker Compose for small deployments or via a Helm chart for larger ones, but it also means an outage or misconfiguration in that stack can lock out every downstream application that relies on it for login.
A hardening checklist worth following
- Enforce MFA on every administrator account, not just end-user logins.
- Maintain break-glass accounts with an offline recovery path that doesn't depend on the IdP itself being up.
- Allowlist the relying parties (the applications) permitted to authenticate against each provider, rather than leaving registration open.
- Version and back up the Authentik configuration separately from application data, so a bad change can be rolled back quickly.
- Monitor authentication failures and admin actions as production telemetry, feeding the same alerting pipeline as any other critical service.
None of this is specific to Authentik — it applies to any self-hosted identity plane — but Authentik's growing adoption among MSPs makes it a reasonable example to hang the checklist on. The practical takeaway is that "self-hosted" and "hardened" are not the same claim: the first is a deployment choice, the second is a list of operational steps that has to be followed after the deployment is live.
Sources: GitHub — goauthentik/authentik, authentik.io.