Authelia vs Pocket ID
Editor take
Choose Authelia for apps with no login of their own and for passwords, keys or TOTP. Choose Pocket ID for passkey sign-in and for users managed in the admin UI.
Where they differ
Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.
Authelia
Where Authelia is stronger
- Guards apps with no loginForward auth asks about every request from your proxy, so an old app with no sign-in still gets the gate; Pocket ID needs a separate authentication proxy for that.1
- Passwords, keys, TOTP or Duo pushA password from a YAML file or LDAP as the first factor, then WebAuthn keys, TOTP codes or Duo push; Pocket ID has no password or TOTP fallback.2
Pocket ID
Where Pocket ID is stronger
- Passkey sign-in, nothing to phishNo password or TOTP code to leak: a passkey on a phone, in a password manager or on a hardware key, plus a one-time code to enrol a device.3
- Users and groups in the admin UICreate a user, send a login code and sort people into groups under Administration; Authelia reads its users from a YAML file or an LDAP server.4
Authelia vs Pocket ID: specs side by side
Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.
Common questions
Does Pocket ID work with apps that do not support OpenID Connect?
Only through an authentication proxy. Apps that speak LDAP or SAML, or have no login at all, need a proxy service in front that asks Pocket ID. Authelia is that kind of service itself: your reverse proxy asks it before each request.
Do Pocket ID and Authelia support passwords?
Authelia does, from a YAML file or an LDAP server, with WebAuthn keys, TOTP codes or Duo push as a second factor; its passkey sign-in is off by default and counts as one factor. Pocket ID has no password: users sign in with passkeys, or with a one-time login code an admin sends.
How does someone sign in to Pocket ID for the first time?
An admin opens the user in Administration, chooses Login Code and sets how long the code lasts. The person signs in once with the code, or with the emailed one once SMTP is set up, and Pocket ID then asks them to add a passkey, which is how they sign in from then on.
What do Pocket ID and Authelia need to run?
Each is a single Go container that keeps its data in SQLite, and both have to be served over HTTPS, so put them behind a reverse proxy. Authelia can move to PostgreSQL, with Redis recommended for sessions once more than one instance runs.
Sources: Authelia docs and Pocket ID docs.