Account and Security

简体中文 | English

Administrator Account

One IPChronicle installation has one local administrator account. On first startup, when config.db has no account, the username and password come from .env; both default to admin. The system recommends changing default credentials but does not block continued use.

After signing in, change the username, password, and interface language under Settings > Account. Editing bootstrap credentials in .env does not overwrite an existing account.

Two-Factor Authentication

The account page can enable TOTP two-factor authentication. Verify that the authenticator generates a valid code before completing enrollment. A server operator can disable TOTP through a local Compose command. The product exposes no remote account-recovery API.

Sessions and Transport

Administrator sign-in uses persistent server-side sessions. Access through an HTTPS reverse proxy and configure trusted proxy sources correctly. IPChronicle allows an administrator to use HTTP intentionally but displays a security warning.

An Agent exchanges the shared enrollment key for a node-specific credential during its one-time enrollment. The shared key is not the node's ongoing identity credential. Credentials and proxy secrets are never echoed in the administration interface.

Local Password Recovery

Only an operator with server-level Compose access can run these commands. They revoke every existing administrator session:

read -r -s IPCHRONICLE_RECOVERY_PASSWORD
printf '%s\n' "$IPCHRONICLE_RECOVERY_PASSWORD" |
  docker compose --env-file .env -f compose.yaml exec -T center \
    /usr/local/bin/ipchronicle-center admin reset-password --password-stdin
unset IPCHRONICLE_RECOVERY_PASSWORD

docker compose --env-file .env -f compose.yaml exec -T center \
  /usr/local/bin/ipchronicle-center admin disable-totp