| Summary | Optional support for 2-factor authentication |
| Queue | Horde Base |
| Queue Version | Git master |
| Type | Enhancement |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | aaronp (at) critd (dot) com |
| Created | 02/19/2016 (3401 days ago) |
| Due | |
| Updated | 03/08/2016 (3383 days ago) |
| Assigned | |
| Resolved | 03/08/2016 (3383 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Optional support for 2-factor authentication
Queue ⇒ Horde Base
Milestone ⇒
Patch ⇒ No
by distant IPs trying to send spam email using compromised user
accounts. Of course a big part of preventing this from happening is
educating our users on password safety, expiring weak passwords in
favor of newer, stronger passwords, etc. We're working hard on that,
but until the time where our users passwords are 100% strong, safe,
and secure (i.e. never), we'd appreciate additional tools to help
prevent or at least mitigate these risks.
One of the options that came to mind was support for 2-factor
authentication on the login screen. We would prefer if users could
somehow opt-in to 2-factor authentication so that not every user would
have to learn how to use it at once. If a per-user opt-in system is
not possible or not practical, than an all-or-none approach would be
fine too. My initial preference would be for Google Authenticator
support, but other options might be just as good or better.