Nothing in docs/ explains the built-in authenticator: that Schuly can hold TOTP secrets at all, how to add one by scanning or by entering a setup key, where the codes then appear, or that the secret is kept on the device.
It comes up in two different places and they are easy to confuse:
- The Authenticator screen, for codes you want to read and type somewhere else - signing in to Microsoft, for instance.
- The 2FA secret row on a school connect form, where the secret is stored so Schuly can generate the code itself during background refresh, rather than for you to read.
The getting-started walkthrough mentions one-time codes in passing but never says how to set one up, and architecture-modes.md covers the vaulted seed from the implementation side only.
Should be written for someone enrolling a new device, including the step where the other service asks for a code to confirm - see #459.
Nothing in
docs/explains the built-in authenticator: that Schuly can hold TOTP secrets at all, how to add one by scanning or by entering a setup key, where the codes then appear, or that the secret is kept on the device.It comes up in two different places and they are easy to confuse:
The getting-started walkthrough mentions one-time codes in passing but never says how to set one up, and
architecture-modes.mdcovers the vaulted seed from the implementation side only.Should be written for someone enrolling a new device, including the step where the other service asks for a code to confirm - see #459.