Strong sign-in
A password and a second step are good; for the applications that matter most, 5.1 lets you ask for more. A strong sign-in policy requires one or two strong factors – a passkey and an authenticator app – and it can be set at every level:
- for the server and per environment, in the server's settings (six
$signIn.strong.*settings) and on ServerAdmin's Sign-in page; - per application, in its definition – ServerAdmin's application dialog offers the presets Off, Strong, Stronger and Custom and shows the policy in effect – or with six
-strong*options on the server's command line; - per module, in its settings, and in the application's own code (
StrongAuthPolicy,StrongAuthState,IUserAuthenticationStrong), which can also ask a signed-in user to confirm a sensitive step.
The strictest rule wins. A value above what the server supports stops the server at start with exit code 9 and one SEVERE line naming it, and iiziGo marks it in the editor.
The SignIn module guides the user through it: “A stronger sign-in is needed” says what is missing and on which kind of device it can be set up, an enrollment walks through “Step 1 of 2” and “Step 2 of 2”, “Try another way” offers the other factor, and “Confirm it is you” asks again before a sensitive action. The screens are in English, French and Swedish.
An administrator who is locked out by a strong policy is let back in by the break-glass file conf\reset-second-factor.txt: at its next start the server resets the second factor, recovery codes, passkeys and signed-in devices of the one administrator the file names, waives the policy for that account's next sign-in only, writes one SEVERE line and deletes the file.
Account lock
Failed sign-ins no longer disable an account. After 15 failed sign-ins the account is locked for 30 minutes; each further lock doubles the time, up to 24 hours. Every lock is a security event, ServerAdmin's Edit user shows “Locked until”, and an administrator can “Unlock account”. A password reset – by the user with “Forgot password?” or by an administrator – ends the lock too, and is recorded. A lock is mailed to the user's verified address at once, whatever the user's mail setting, and says until when the account is locked; a lock started by a wrong password outside the sign-in page – a password change, a confirmation of the password in a signed-in session, the Push API – is mailed and recorded as well. An attempt refused without being checked, during a wait or a lock, is not counted as a failed sign-in.
Failed sign-ins
The server records every failed sign-in on a known account. The user sees the list in the SignIn module, can clear it and choose mail notices; the administrator sees it in ServerAdmin's “Devices and security” and can clear it. A mail goes to the user's verified address only, throttled by the settings $signIn.failedSignInMailMinutes (5 minutes by default) and $signIn.failedSignInWarningsPerHour (10 by default) – and at once when the password was right or the account is a sensitive one. The mails are in English, French and Swedish.
Sign-in records and security events
The server keeps a record of every sign-in – when, from which device, from which address and from which approximate place – and a log of security events, in its database. Both are deleted after $signIn.signInRecordDays days (90 by default). ServerAdmin's “Devices and security events” dialog shows a user's devices with their sign-ins, signs out a single device, and lists the failed sign-ins and the security events, filtered by severity. In the SignIn module the device list tells the user since when and where each device signed in, with a one-line notice that the time, the approximate location and the time zone are stored.
For developers: a session can log its own security events (logSecurityEvent), and GeoProps.requestQuietLocation asks for a device's location without ever prompting the user.
ServerAdmin's Sign-in page
A new page shows and edits every sign-in setting of the server – the second step, staying signed in, accounts, links, password policies, passkeys per environment and the strength of the sign-in – each with its default. Every change is checked, logged with the key it changed, and guarded: the page will not let the administrators lock themselves out, and it asks for a recent second step before it lowers their protection. A changed password policy applies to the next sign-in, without a restart.
In Edit user, an action that needs a recent sign-in opens a “Confirm it is you” dialog that names the administrator's own account, and the administrator's own account cannot be deleted or disabled from their own session.
Deleting and disabling a user
Deleting a user ends all of the user's open sessions at once and deletes the user's device tokens, Push subscriptions, authenticator app and passkeys; ServerAdmin reports what was removed. Disabling a user signs out the user's devices and stops Push Notifications to them.
Sessions and reconnection
When a page's connection breaks – a network change, a phone app in the background – and it reconnects, it now presents a secret token that only that page received with its session, and the token changes at every reconnection. Session IDs are longer (32 hexadecimal characters), every server log line shows them masked (FE4D...441A-1), and iiziGo's Server Monitor shows the full ID. A reconnection without a token is still accepted onto a session whose connection was lost, never onto one whose page still answers; 5.2 will require the token.
What a reverse proxy should log: Upgrading from 5.0.
Secrets stay secret
- A password property never prints its value in a log line, an exception text or a listing.
- The Server Monitor's copy of a development server's settings leaves every value marked secret empty.
- ServerAdmin's Domains dialog no longer sends a stored key store password to the Browser: leave the field empty to keep it, type a value to replace it.
- A user-profile URN answers the signed-in user's own profile only, and never its PIN code or recovery answer.
- A user's published files, such as a profile picture, get an address that names neither the user ID nor the user name, and a file that is unpublished stops being served at once.
- The Push API's HTTP Basic sign-in follows the rules of the interactive sign-in: the account lock, the failure count and the throttle per source. A source that is held back gets status 429 with
Retry-After. - A script that fails to load is logged without the parameters of its address, so an application key in that address stays out of the logs.