Legacy RADIUS server IPs will be deprecated on Dec 17, 2018. Please see this KB for more info.

Support Center

Using Multifactor Authentication with JumpCloud

Summary

These instructions show you how to set up multi-factor authentication (MFA) for users of JumpCloud using the JumpCloud User Portal. Once setup for a user, MFA can be used to authenticate that user when signing into the JumpCloud User Portal, or other resources protected by JumpCloud MFA.


About JumpCloud MFA

JumpCloud MFA utilizes authenticator codes known as Time-based One-Time Password (TOTP) Tokens. Once MFA is setup for a user, the user will be required to enter these tokens when signing into a JumpCloud resource that has been enabled for MFA protection by a JumpCloud Admin. Each user is set up independently, and will have their own TOTP tokens. This process requires a TOTP application that will generate these tokens for the user, generally using a mobile device. Any application that can generate a six-digit SHA-1 based TOTP token should be able to be used with JumpCloud MFA. Several apps qualified to work with JumpCloud are:


Preparing Your Users

We advise administrators to educate their users in advance of enabling MFA to prevent potential confusion over the change in workflow.

  • Once an admin enables JumpCloud MFA for a user, the user will receive an email notifying them they are now required for MFA, and notify them of how long they have to enroll in MFA before the MFA token is required at login to the user portal.
  • Following the link in the email, or logging into the User Portal will give the user access to their TOTP key and QR code to scan into a qualified MFA app token generator app, until their enrollment period expires.
  • Once the user completes MFA setup, the JumpCloud User Portal will require email address, password, and TOTP Token at sign in.  Additionally, for any MFA-enabled systems, users will be prompted for MFA when logging into those systems once they have completed setup.


Requiring Multi-Factor Authentication on an Individual User Account

Instructions

  1. Edit a user or create a new user in the Admin Console.
  2. Enter other user configuration details.
  3. Select the 'Require Multi-Factor Authentication for User Portal' checkbox.
  4. Select the number of days the user has to enroll in MFA before they will be required to have MFA at login.  The number of days can vary between 1 and 365, and will be defaulted to 7 days.
  5. Select ‘Save' to save the user.
  6. New users will receive a welcome email if their initial password was not set, and will be prompted to complete their MFA setup when they next login to the User Portal.
  7. Existing users will receive an email notifying them they have been requested to set up MFA.


Requiring Multi-Factor Authentication on Existing Users in Bulk Actions

Instructions

  1. Select users you would like to require MFA for.
  2. Expand the “more actions” drop down and select “Require MFA on User Portal”
  3. Select the number of days the user has to enroll in MFA before they will be required to have MFA at login.  The number of days can vary between 1 and 365, and will be defaulted to 7.
  4. Select “require” to add this requirement to the selected users.


Extending Time for a User to Enroll in MFA

If a user has been locked out because their allotted time for MFA enrollment has expired, or is about to expire, you may want to extend the enrollment period for the user.

Instructions

  1. Edit the user that needs an extension in the Admin Console.
  2. Select the user's MFA status indicator to show the MFA options menu.
  3. Select the 'Reset MFA' option from the menu to display the reset MFA modal.
  4. Specify the time period allotted for the user to enroll, starting from today, and submit.
  5. The user will be notified of the enrollment period change, and subsequently will follow the standard MFA enrollment process.


In Case of Device Loss or Failures

Because the device containing the TOTP key may be a single point of failure, in case of loss or breakage, it's recommended to record and store the TOTP value in a safe place as a backup. Most apps that generate TOTP tokens allow the TOTP key to be entered manually, which means it can be typed in rather than scanning the QR code in order to restore the ability to generate tokens on a new device or app.

Alternatively, if a user loses their ability to generate tokens, a JumpCloud administrator can perform an MFA reset for the user through either the Users list bulk actions or the Details tab for a single user in order to clear the previous TOTP key, and re-enter an enrollment period.

Instructions

  1. Edit the user that needs the MFA reset.
  2. Select the user’s MFA status to display the MFA operations menu.
  3. Select ‘Reset MFA on User’ from the menu.
  4. A window will appear.
  5. Select the number of days they will have to complete their setup.
  6. Press the ‘Reset’ button.
  7. The user should be able to now login without MFA, and be prompted to reconfigure their MFA prior to the enrollment expiration.


MFA Resource Availability

MFA resource protection is available on the following JumpCloud-managed resources:

  • User Portal login
  • Mac desktop login
  • Linux SSH login
  • SSO/SAML application login
  • Admin Portal login*

Once MFA setup has been completed by a user, MFA will be enforced for that user on any MFA-protected resource. For example, if MFA is enabled for a given Linux server, and User A has completed MFA setup, they will be prompted for a token when signing into the protected Linux server. If User B has not completed MFA setup, they will not be prompted when signing into the same Linux server.

* Admin Portal MFA protection follows a separate MFA enrollment process


User Eligibility

Note: Active Directory owned users created using the JumpCloud Active Directory Bridge do not have the option to enable Multi-factor Authentication for the User Portal.


User Workflow - Initial Setup

  1. The user will receive an email, stating they are required to setup MFA for JumpCloud.
  2. They will click the link in the email OR log into the JumpCloud User Portal directly.
  3. They will be prompted for username and password.
  4. They will press the ‘user login’ button.
  5. Username and password will be authenticated.
  6. They will be prompted to set up multi-factor authentication, including links to Google Authenticator on the iOS App Store, and the Google Play Store. They are free to dismiss this prompt until the enrollment period ends.  Upon dismissing the prompt, they will be reminded of the number of days remaining in enrollment.
  7. Upon pressing ‘continue’, they will be provided a QR code and TOTP key string that can be used to configure a qualified MFA token generator app, and prompted for their first TOTP token produced by the token generator app.
  8. For backup purposes, this would be the time to copy and paste their the TOTP key string below the QR code and store it in a secure location.
  9. Upon submission, they will be notified that MFA setup is complete


User Workflow - Expiring Enrollment

When a user has an enrollment that is expiring, they will be sent a reminder 24 hours in advance notifying them that MFA enrollment will expire. Once their enrollment has expired, they will be locked out of the User Portal until their MFA requirement is removed by an administrator or their enrollment time is extended using the ‘Extending Time for a User to Enroll in MFA’ process above.


User Workflow - User Portal Login After MFA Setup Completed

Once a user has completed MFA setup, the admin has required MFA on the user portal for the user, and the Google Authenticator is installed and linked with the user account, the login experience will be as follows for the User Portal:

  1. The user will go to https://console.jumpcloud.com
  2. They will be prompted for username and password
  3. They will press the ‘user login’ button
  4. Username and password will be authenticated
  5. They will be prompted for the Multi-Factor Authentication verification code, which they should populate with their TOTP token from the qualified MFA app of they have chosen (e.g. Google Authenticator). The user will have 60 seconds to input the digits from their MFA app into the JumpCloud OTP field. Nearing the end of the 60-second cycle, their MFA app will indicate the current key is about to expire, and the user should wait until a fresh key is generated.
  6. They will press the ‘user login’ button
  7. Their TOTP token will be authenticated
  8. They will be logged into the User Portal

Related

 

 

Last Updated: Dec 04, 2018 04:54PM MST

Related Articles
31b11a79e2c94470a66430cfe6d3eecd@jumpcloud.desk-mail.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete