long-time overdue +1 
Sorry, I didn't want this but since implementation was started in ZBXNEXT-6876 there is no reason to keep this open.
[ZBXNEXT-4966] Provide support for RFC 6238 Time-based One-time Password Algorithm (OATH-TOTP) Created: 2019 Jan 18 Updated: 2024 Feb 02 Resolved: 2024 Feb 02 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F) |
| Affects Version/s: | 4.0.3 |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Major |
| Reporter: | Marco Hofmann | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 6 |
| Labels: | 2FA, frontend, security | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Debian9 amd64 |
||
| Issue Links: |
|
||||||||
| Description |
|
Due to many password and security breaches in the last years, account security has become one of the top priorities for every web platform that provides sensitive data. Nearly all big players have implemented OATH-TOTP by scanning a QR Code with your smartphone, which can then be used with Google Authenticator or Authy for example:
As a IT service provider, we provide our Zabbix Frontend public available via Apache HTTPS, so customers have Read-Only access to all their data. To further secure the frontend, Two Factor Authentication is a must in the year 2019 imho. Further information: https://en.wikipedia.org/wiki/Google_Authenticator |
| Comments |
| Comment by John Wayne [ 2020 Oct 03 ] |
|
long-time overdue +1 |
| Comment by dimir [ 2024 Feb 02 ] |
|
Sorry, I didn't want this but since implementation was started in |