Login

Last updated

/jabali-admin redirects to the Kratos login flow at /auth/login.

Flow

  1. Username + password. The username is the login identifier; the email is not used to sign in.
  2. If TOTP 2FA is enrolled: redirect to Two-Factor Challenge.
  3. Session cookie set; redirect to /jabali-admin/dashboard.

Sessions are managed by Kratos. The panel itself does not store passwords or session tokens.

Log in via the panel hostname, not the server IP. Kratos is same-origin — its login cookies, CSRF tokens, and allowed return URLs are bound to the panel hostname (FQDN), so opening the panel by raw IP fails the flow with “could not reach identity service”. The login page shows a hint when you reach it by IP.

First admin

Created by the installer. The admin one-time recovery URL is printed at the end of bash install.sh. If you missed it:

jabali user password <admin-username> --link

…emits a Kratos recovery URL. Open it → set a password → optionally enrol 2FA. The recovery flow requires auth.kratos.admin_url reachable (installer-wired by default). Direct password reset is also available:

jabali user password <admin-email>

(The legacy jabali admin one-time-login command was removed.)

Locked out

If the only admin lost their password or 2FA:

jabali user password <admin-email>          # generate a new password
jabali user 2fa-reset <admin-email>         # strip TOTP + recovery codes

Both bypass HTTP auth (direct DB + Kratos) so they work even when the panel UI is unreachable.

Bruteforce protection

CrowdSec watches kratos.public and nginx.access for failed-auth patterns. Repeated failures from one IP earn a 4-hour BAN decision. See CrowdSec Decisions.

No OIDC

The panel does not act as an OIDC provider (that feature was rolled back; see removed-features). Login is local-account-only via Kratos.