SSH, the secure shell, is often used to access remote Linux systems. Because we often use it to connect with computers containing important data, it’s recommended to add another security layer, such as the second factor.
In this guide, we will show how to leverage the TOTPRadius appliance to organize SSH access to your Ubuntu server using local LDAP or Azure AD as the primary authentication factor, and TOTP factor from TOTPRadius as the secondary factor. The secondary authentication factors available with TOTPRadius can be a mobile authentication app or a hardware token.
Login to the Ubuntu machine using an account with administrative privileges. Then, install the module using the command below
$ sudo apt-get install libpam-radius-auth
Open the configuration file and add the RADIUS server configuration
sudo nano /etc/pam_radius_auth.confAdd the server as shown in the example below, where 192.168.1.1 is the IP address of your TOTPRadius appliance and shared_secret should match the RADIUS secret (to be configured in the next chapter)
# server[:port] shared_secret timeout (s) 192.168.1.1 hwxa30lqwcr 10Configure the SSH server to use this PAM module as the authentication source. Open the /etc/pam.d/sshd file
sudo nano /etc/pam.d/sshdAnd add the following line
auth sufficient pam_radius_auth.soMake sure this is added just before the following line
@include common-authThe resulting file should start with the lines similar to the shown below
# PAM configuration for the Secure Shell service auth sufficient pam_radius_auth.so # Standard Un*x authentication. @include common-authTo finalize the configuration on the Ubuntu side, you have to create local users with usernames matching the users in the LDAP or Azure AD. Please note that this is a technical restriction of the PAM module. The module can only forward the authentication to TOTPRadius, it is not allowed to create user accounts that do not exist in the system for obvious security reasons. Please note that the password set at this stage can later be removed (alternately, you can generate any random complex password and do not need to record it as it will not be used)
sudo adduser jsmith Adding user `jsmith' ... Adding new group `jsmith' (1002) ... Adding new user `jsmith' (1002) with group `jsmith' ... Creating home directory `/home/jsmith' ... Copying files from `/etc/skel' ... New password: put_any_complex_password Retype new password: put_any_complex_password passwd: password updated successfully Changing the user information for jsmith Enter the new value, or press ENTER for the default Full Name : Room Number : Work Phone : Home Phone : Other : Is the information correct? [Y/n] YIf you want to make sure no authentication with local password is possible (even theoretically), you can specify --disabled-password argument
$ sudo adduser --disabled-password jsmithYou can also pre-add the users from your Azure Directory in bulk using a script similar to below:
sudo adduser --disabled-password --gecos "" user1 sudo adduser --disabled-password --gecos "" user2 sudo adduser --disabled-password --gecos "" user3 ...
--gecos GECOS Set the gecos field for the new entry generated. adduser will not ask for finger information if this option is given.
TOTPRadius will be used as the only authentication method for SSH access. Therefore, the SSH login process will require to supply the username and both the primary and secondary authentication factors in the password prompt. The password supplied by the user is expected to contain both the AD or Azure AD password and the 6 digits OTP. The supplied password is parsed and the OTP gets verified locally, and AD password is checked via AD or Azure AD using the RPOC method. Please note that the Azure AD functionality is available with TOTPRadius v0.2.7 or newer.
The guide below will show using on-premises Active Directory as the primary authentication source (LDAP proxy mode) as an example. Azure AD can also be enabled and used similarly.
► In Main settings, set the Radius secret to the one used in the PAM configuration above
► In Main settings, set 'Allow initial login' value to zero (having initial login allowance is used for self-enrollment, which is not required in this configuration)
► [optional] In the Endpoint IP and subnet fields specify the parameters of your Ubuntu server
► Set LDAP as enabled
► Specify the LDAP server IP/FQDN and the format of the username (%firstname.lastname@example.org or DOMAIN\%username% format, where "DOMAIN" or "domain.local" need to be replaced with the domain name or removed if needed )
► If you decide to allow self-enrollment, make sure "Allow ldap enrollment" parameter is enabled. In the same section, you can also allow re-enrollment and modify the intro text of the LDAP web enrollment page