| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-09-17 | 3.5 kB | |
| v0.6.1 -- Staff recovery-code sign-in fix source code.tar.gz | 2026-09-17 | 1.6 MB | |
| v0.6.1 -- Staff recovery-code sign-in fix source code.zip | 2026-09-17 | 2.1 MB | |
| Totals: 3 Items | 3.8 MB | 0 | |
v0.6.1 — Staff recovery-code sign-in fix
What's fixed
Staff users can now sign in with a two-factor recovery code. On the
staff two-factor screen, the code field stopped accepting input after six
characters. Recovery codes look like XXXXX-XXXXX, eleven characters, so
typing one got cut off and the screen refused it without ever contacting
the server. For a staff user who had lost their authenticator app, that
meant no way back in: there is also no admin-side way to reset someone's
2FA yet (see "Known issues"). The customer and broker portal never had this
limit, and the staff limit had been there since the screen was first built.
Recovery codes are now accepted in lowercase and with stray spaces, on both the staff and portal screens. Some phone keyboards don't capitalise, and a code copied from a saved file can pick up a trailing space; both used to be rejected. The set of valid codes, the rate limit on attempts and the lockout after repeated wrong codes are all unchanged.
What's new
A "Lost your phone? Use a recovery code" link on the staff and portal two-factor screens. Tapping it relabels the field for a recovery code and asks the phone for a full keyboard instead of a number pad, since a number pad can't type the letters or the dash in a recovery code. Tapping "Use your authenticator app instead" switches back. On a computer keyboard the link makes no practical difference: the field accepts either kind of code whichever mode it's in.
Not yet verified
Two things about this release have not been checked by a person yet, and you should know that before relying on it:
- The phone keyboard behaviour is reasoned from the code, not verified on a real device. The field asks for a number pad normally and a full keyboard in recovery mode, but each phone's browser makes the final choice, and no real phone has been checked yet.
- The recovery-code link has been exercised by automated browser tests, not looked at by a human. The tests press real keys, check the wording, and sign in end to end on both staff and portal. A manual check is planned after the project's verification server is upgraded to this release.
If something about the new link looks or behaves wrong on your phone, please report it.
Is any action needed beyond upgrading?
No. No database migration, no new environment variable, no re-enrolment. Existing recovery codes keep working.
Also in this release
See CHANGELOG.md (github.com),
the [0.6.1] section, for the full detail.
Upgrading
:::bash
cd /opt/openestate-src/deploy/native
sudo ./upgrade-native.sh --ref v0.6.1
Full procedure (backup, rollback behaviour, troubleshooting): Installation Guide.
Known issues
There is still no admin-side way to reset a user's 2FA. With this fix,
a recovery code is a working way back in for staff who lose
their authenticator. It is also the only one: if someone loses both their
authenticator and their recovery codes, there is no product path to
recover the account. reset-admin-password.sh resets the password but does
not clear 2FA. If you enable 2FA broadly, make sure recovery codes are
stored somewhere safe, or keep more than one admin account enrolled.
The known issues listed in the v0.6.0 release notes still apply.