Skip to content

Document two-factor authentication - #51

Draft
trasher wants to merge 2 commits into
developfrom
feature/2factor
Draft

trasher wants to merge 2 commits into
developfrom
feature/2factor

Conversation

@trasher

@trasher trasher commented Sep 17, 2026

Copy link
Copy Markdown
Member

No description provided.

Five places, one per question a reader arrives with:

- preferences: the four policies, and that turning it back off deletes
  nothing;
- generalities: how a member enables it, which applications to use, and
  that the ten recovery codes are shown once and want printing;
- members: how an administrator resets one, with the reminder that a
  phone call asking for a reset is exactly how somebody would try to get
  a protection removed;
- FAQ: clock drift first -- it refuses every code while everything else
  looks normal -- then the single use of a code, the lost device, and the
  super administrator, which has no recovery codes and is cleared from
  the database;
- post installation: keep the server clock right, and keep an access to
  the database before enabling it on the super administrator.

No screenshots yet: the interface is still under review.
They are written and tested but not offered in 1.3.0: under a compulsory
policy a server clock that drifts or an enrolment that goes wrong puts a
whole association outside its own instance, and the only way back is a
command in the database. Two policies documented instead of four, and
what is missing said as such rather than left out.

Since nothing forces anybody to enrol, the invitation administrators and
staff members get at login is described where a reader meets it, with
what the two declining buttons remember and for how long.

Two more entries from what shipped: a server clock moving backwards,
which refuses every code as a replay until it catches up -- and it has
its own way out, distinct from plain drift -- and the limits of a reset,
which only ever goes downwards.

The paragraph on clearing the super administrator no longer mentions
being sent back to enrolment: no policy can require that in 1.3.0. It
says how to turn the second factor off for everybody instead, which is
what somebody reading that page at two in the morning is after.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant