Cloud Authentication Service User Requirements

Document created by RSA Information Design and Development on Jul 14, 2016Last modified by RSA Information Design and Development on Nov 15, 2019
Version 45Show Document
  • View in full screen mode
  

The Cloud Authentication Service can prompt users for authentication through RADIUS clients, a browser to access web applications, or the RSA SecurID Authenticate app. Your users must meet the following requirements in order to authenticate.

 

Note:  RSA does not support using the RSA SecurID Authenticate app on a rooted Android device, a jailbroken iOS device, or a rooted Windows device. Do not allow such a device in your deployment.

Supported Languages

The Cloud Authentication Service can prompt users for authentication in the browser or in the Authenticate app in the following languages:

  • English

  • Chinese

  • French

  • German

  • Japanese

  • Portuguese

  • Spanish

Browser Requirements

                  
Browser Minimum Required Version
Internet Explorer 11

Microsoft Edge

Chrome (PC or desktop, Android)

Firefox

Safari (Mac, iOS)

Latest
 

RSA SecurID Authenticate Device Requirements

App Store Download Requirements

To download RSA SecurID Authenticate from an app store, the user's device must meet the following requirements:

                       
Device Minimum Operating System Version
Android6.0
iOS11.0
Windows PC

Windows 10 Version 1511

Minimum Supported OS and App Versions

RSA updates the RSA SecurID Authenticate app on a regular basis. RSA recommends that users always update to the latest version of the app. However, if users are unable to, the following table lists the supported minimum requirements for the Authenticate device.

                            
Device Minimum Required Operating System VersionMinimum Required App Version
Android5.02.3
iOS10.02.2
Windows PC

Windows 10 Version 1511

Note:  If you use Approve or Device Biometrics, ensure that your users' devices can access the VIP and IP address ranges used by the Windows Notification Service. For more information, see Windows Notification Service (WNS) VIP and IP Ranges.

2.0
 
 

FIDO Token Requirements

The FIDO Token can be used for primary authentication (for example, the user is prompted to sign in with a FIDO token instead of entering a password after entering a user ID) or for additional authentication (for example, after entering a user ID and password, the user is prompted to sign in with your FIDO token). The system requirements vary based on the authentication type.

System Requirements for FIDO Primary Authentication

                          
FIDO2 Token Operating System Browser and Minimum Required Version
  • FIDO-certified security key, for example a USB security key.

  • FIDO token must require user verification, such as a PIN or biometric.

    User must set up user verification on the token before using the token to authenticate.

  • Token must already be registered with RSA SecurID Access. For instructions, see Registering Your Device.

Windows 10 Version 1803

Note:  Some FIDO2 tokens might not work with this operating system version.

Chrome 76

Windows 10 Version 1903

Note:  This operating system version supports setting up token multifactor authentication when authenticating.

  • Microsoft Edge 44
  • Chrome 76
  • Firefox 69
Mac OS

Chrome 76

System Requirements for FIDO Additional Authentication

                          
FIDO2 TokenBrowser Minimum Required Version

FIDO-certified security key, for example a USB security key.

Microsoft Edge

44.17763.1.0
Chrome

PC or desktop: 67

Android: 70

Firefox

PC or desktop: 60

Android: 63

Note:  The FIDO Token might not work on browsers that run on a virtual machine.

Authentication Method Requirements

  • Device Biometrics requires an iOS device that supports Touch ID or Face ID, a Samsung or Android version 6.0 device with a fingerprint sensor, or a Windows device with Windows Hello enabled.

  • SMS Tokencode requires a phone that can receive SMS messages.

  • Voice Tokencode requires a phone that can receive voice calls.

 

 

We want your feedback! Tell us what you think of this page.

You are here
Table of Contents > Users and Devices > Cloud Authentication Service User Requirements

Attachments

    Outcomes