Two factor authentication (2FA) is more and more emerging which is good to enhance security. Since the release of IPA4 it comes with 2FA included.
Over time I made a lot of experiments and experience I wanted to share with you. Its is easy to set up and maintain as long as you use it only for system authentication. If you are using such things as webmail, it fails. This post shows you the capabilities as they are of today. Almost all bad issues apply not only to Fee(IPA) but 2FA in general.
All your systems are Fedora 21, RHEL 7.1 or Ubuntu 14.02 all is working fine as the included SSSD is new enough to handle 2FA. All kerberized services can be used with 2FA w/o logging in again during the validity of your Kerberos ticket. Very convenient, very secure.
3rd Party applications can use LDAP authentication (Depending on the usecase)
Systems with older distributions such as RHEL6.6 come with a SSSD version which is to outdated to handle kerberized 2FA at all. This will probably change soon.
- Use LDAP authentication (See later on)
- Use a Jump host with a recent Linux distribution
If you are logging in to your workstation with a local user, you can not grab a Kerberos ticket with
kinit and use this ticket further on. (i.e for ssh logins on remote server, mail etc.)
- Switch to a IPA managed user if your workstation is recent enough.
- Use a Jump host with a recent Linux distribution
- Wait until krb5-PAKE is in place, software is being developed, see http://k5wiki.kerberos.org/wiki/Projects/Improve_OTP_deployability and https://github.com/npmccallum/krb5-pake
Looks like most mobile applications such as the IMAP client in Android do not prompt for the password, they expect it configured. Needless to say that you can not reconfigure the password each time you want to check your emails with your phone.
- 3rd party email app? One that prompts for the password if needed
- Configure IPA to accepts password and 2FA which lets the user choose to either use the password only or 2FA. Needless to say that this makes 2FA less useful as people tend to be lazy
- Turn off 2FA in IPA and use a Yubikey with a static password (spit password). This is not a real 2FA it is a single password split in two. Password change is a horror.
Accessing Webmail clients (I tested roundcube mail) causes headaches as well. They authenticate the users with IMAP and use this credentials to access the mail storage. As the second factor is a one time password (OTP) this will result in failure to retrieve mails after logging in.
Workaround: Same as for mobile applications. I would appreciate if someone can point me to a webmail software which can handle this.
One sentence: Offline usage does not work because it can not work.
- Create a local user and use a Yubikey and configure it with a static password (split password). This is not a real 2FA it is a single password split in two. Password change is a horror.
- Install a IPA server on your Notebook 😉 This will scale up to 18 Notebooks (plus two replicas in the datacenter) but introduce a lot of other problems, so: Not seriously to be considered.
LDAP Authentication as a Workaround
Configure PAM/SSSD to use LDAP authentication for your users. IPA comes with a very nice feature called ipa-advise.
[root@ipa1 ~]# ipa-advise config-redhat-nss-pam-ldapd #!/bin/sh # ---------------------------------------------------------------------- # Instructions for configuring a system with nss-pam-ldapd as a IPA # client. This set of instructions is targeted for platforms that # include the authconfig utility, which are all Red Hat based platforms. # ---------------------------------------------------------------------- # Schema Compatibility plugin has not been configured on this server. To # configure it, run "ipa-adtrust-install --enable-compat" # Install required packages via yum yum install -y wget openssl nss-pam-ldapd pam_ldap authconfig # NOTE: IPA certificate uses the SHA-256 hash function. SHA-256 was # introduced in RHEL5.2. Therefore, clients older than RHEL5.2 will not # be able to interoperate with IPA server 3.x. # Please note that this script assumes /etc/openldap/cacerts as the # default CA certificate location. If this value is different on your # system the script needs to be modified accordingly. # Download the CA certificate of the IPA server mkdir -p -m 755 /etc/openldap/cacerts wget http://ipa1.example.com/ipa/config/ca.crt -O /etc/openldap/cacerts/ipa.crt # Generate hashes for the openldap library command -v cacertdir_rehash if [ $? -ne 0 ] ; then wget "https://fedorahosted.org/authconfig/browser/cacertdir_rehash?format=txt" -O cacertdir_rehash ; chmod 755 ./cacertdir_rehash ; ./cacertdir_rehash /etc/openldap/cacerts/ ; else cacertdir_rehash /etc/openldap/cacerts/ ; fi # Use the authconfig to configure nsswitch.conf and the PAM stack authconfig --updateall --enableldap --enableldapauth --ldapserver=ldap://ipa1.example.com --ldapbasedn=cn=compat,dc=example,dc=com [root@ipa1 ~]#
The output actually reflects your environment, example.com will be replaced with your domain, its copy-paste ready. I love this feature 🙂 For other Linux systems, run
ipa-advise without parameters to see which advises are available.
2FA works well, convenient and secure in a datacenter and office environment. Notebooks are fine as well as long as there is a network connection available. The mobile world (Smartphones and Tablets) is not yet ready for 2FA. Some issues can be worked around (with some drawbacks) while others render 2FA not usable at all (offline usage).
Hopefully there will be some smart solutions available for mobile usage soon, as mobile usage causes the most of the security headaches.