- Admin → Settings → Who can add aircraft: administrators only (the
default) or everyone. Adding an aircraft or importing a .sam.zip makes
you its Owner, so this decides who can become one.
- A signing invitation from an Owner of the aircraft (or an
administrator) lets the outside mechanic create an account for the
invited address again, with a password or by signing in with SSO;
checked when it's used. Others' signing invitations still need an
existing account, and say so.
- Docs: who makes accounts, the new setting.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Anyone can add an aircraft and so manage its people, so invitations from
non-administrators could bring in new accounts without an administrator.
- An invitation makes a new account only if whoever made it is still an
administrator when it's used; an aircraft's Access page invitations are
for people who already have an account (its welcome page says so).
- Signing invitations no longer make accounts: the mechanic needs one
first, and the owner is told when they don't have one.
- With SSO, "Continue with <provider>" on an administrator's invitation
makes the account and accepts the invitation (only for its address when
it has one), so invitations work without OIDC_AUTO_CREATE_USERS. That
setting stays, documented as giving accounts without an invitation; the
Authentik example now leaves it off.
- Docs: who makes accounts (guide, README, Authentik, .env.example, API).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Views use lazy t(".key") lookups; sentences with values or links stay
whole (interpolation, _html keys); counts use one/other plurals
- Stored-value labels (statuses, types, priorities...) are LabelSets read
from labels: in the current locale; field names and validation messages
under activerecord:; flash and activity text under flash:
- Services, models, helpers, mailer subjects, the logbook PDF, procedures
templates, records package README and transcription warnings localized;
the PDF reuses LogbookEntry#certification_statement instead of a copy
- Scripts read js: strings from a JSON tag via app/javascript/i18n.js
- Dates through I18n.l (app, weekday, month_year, long formats); html lang
follows the locale
- APP_LOCALE picks the language (falls back to English); missing
translations raise in development and tests
- README: Translating section and APP_LOCALE
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 10 failed sign-ins in a row (password, authenticator code, or password
at signing) lock an account for 15 minutes from any address; the user
is emailed; admins can unlock. Same message as a wrong password.
- Passwords: at least 12 characters (max 72), refused if found in Have I
Been Pwned (k-anonymity range API; fails open; PWNED_PASSWORDS_CHECK=false)
- Optional TOTP (authenticator app) with 10 recovery codes for password
and emailed-link sign-in, and at signing (auth method password_totp);
codes accepted once; admins can reset; SSO sign-in unaffected
- Demo/test passwords updated; guide, README and procedures document
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Sign an entry: review exactly what's certified, choose a current
certificate (eligibility checked: pilot only for preventive maintenance,
inspections need their result and time), re-enter the password or sign
in again with SSO (prompt=login, within 5 minutes), and confirm the
"Certified by" statement (43.9 return to service, 43.11(a)(5) for
inspections, preventive maintenance for pilots)
- The signature stores signer, certificate, statement, UTC time, how they
authenticated, IP/browser, a SHA-256 fingerprint of the entry's content
and a readable snapshot; an HMAC seal covers the signature record. Status
shows Valid / Superseded / Altered since signing. The signer is emailed
- Signed entries (and their sub-components) can't be edited or deleted;
a correction entry, once signed, supersedes the original (kept)
- Owners invite an outside mechanic by email to sign one entry: one-time,
14-day link; they create or use their own account and certificate and
see only that entry
- Admins can disable accounts (signed out, can't sign in or sign; past
signatures kept); users with signatures can't be deleted
- Printouts show the electronic signature and fingerprint; archives carry
signatures (marked imported, with their origin) and corrections
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>