Summary | Two Factor Authentication |
Queue | Horde Base |
Queue Version | Git master |
Type | Enhancement |
State | Accepted |
Priority | 1. Low |
Owners | |
Requester | jurekam (at) gmail (dot) com |
Created | 07/12/2015 (3594 days ago) |
Due | |
Updated | 07/02/2020 (1777 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
https://www.linotp.org/
something is done about the reason why (lack of funding), it makes no
sense to keep asking.
Factor authentication would be great to have implemented. I just
switched from a Roundcube install and it had a plugin for it which
worked great. Two Factor authentication has become the standard
these days and your product is lacking in this regard. Please
implement this ASAP.
Factor authentication would be great to have implemented. I just
switched from a Roundcube install and it had a plugin for it which
worked great. Two Factor authentication has become the standard
these days and your product is lacking in this regard. Please
implement this ASAP.
1. configure Horde for PAM-Authentication
2. use the Google authenticator PAM-module, or the pam-u2f-module
for e.g. Yubikey
... and you're done.
Cheers from Stuttgart / BW / Germany
Christoph.
easy as mentioned in my last comment ...
Thus the below PAM-config works, tested e.g. as PAM-config for "su",
it doesn't do so with Horde :-((
PAM-authentication works if I remove the google_authenticator part ...
(just for the records: my system runs on a Debian Jessie amd64)
/etc/pam.d/horde
auth requisite pam_google_authenticator.so forward_pass
auth [success=1 default=ignore] pam_ldap.so minimum_uid=1000
use_first_pass
auth requisite pam_deny.so
auth required pam_permit.so
auth optional pam_cap.so
-->> the login credential with this PAM-config consists of the
user-password and the one-time-password from the Google Authenticator.
E.g. if the user-password is: mysecretpwd
and the Google OTP: 123456
the login credential would be: mysecretpwd123456
but in /var/log/syslog
HORDE: [horde] FAILED LOGIN for haasc to horde (172.16.1.2) [pid 10073
on line 199 of "/var/www/html/horde/login.php"]
HORDE: [gollem] PHP ERROR: Invalid argument supplied for foreach()
[pid 10073 on line 338 of "/var/www/html/horde/gollem/lib/Auth.php"]
... and the login is denied with a error on the Horde-login-screen:
"Cannot make/remove an entry for the specified session (in pam_authenticate)"
Clueless - where is my bug?
Christoph.
Queue ⇒ Horde Base
State ⇒ Accepted
Factor authentication would be great to have implemented. I just
switched from a Roundcube install and it had a plugin for it which
worked great. Two Factor authentication has become the standard
these days and your product is lacking in this regard. Please
implement this ASAP.
1. configure Horde for PAM-Authentication
2. use the Google authenticator PAM-module, or the pam-u2f-module for
e.g. Yubikey
... and you're done.
Cheers from Stuttgart / BW / Germany
Christoph.
Priority ⇒ 1. Low
work, or providing patches. Also, please check the mailing list archive.
Priority ⇒ 3. High
Type ⇒ Enhancement
Summary ⇒ Two Factor Authentication
Queue ⇒ Horde Groupware Webmail Edition
Milestone ⇒
Patch ⇒ No
State ⇒ New
Factor authentication would be great to have implemented. I just
switched from a Roundcube install and it had a plugin for it which
worked great. Two Factor authentication has become the standard these
days and your product is lacking in this regard. Please implement
this ASAP.