Device Registration

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

Device registration binds a device (phone, tablet, or desktop or PC) to a user. It is a prerequisite for using a device to authenticate to a protected application using RSA SecurID Access.

 

Purpose of Device Registration

The purpose of registering a device is to authenticate using methods that are specific to the device, for example, Approve, RSA SecurID Authenticate Tokencode, Eyeprint ID, and Fingerprint Verification on an iOS or Android mobile device. SMS Tokencode, FIDO token, and RSA SecurID token do no require this type of registration.

Note:  Users who do not register a device using the RSA SecurID Authenticate app are not presented with authentication methods that require the app.

A user can register a single device with the RSA SecurID Authenticate app installed.

 

When Device Registration Occurs

A device becomes registered when the user installs the RSA SecurID Authenticate app and follows the prompts in the app. During this process, a user does the following:

  • Accepts the license agreement.
  • Enters the identity source email address (called User ID), your RSA SecurID Access company ID, and the identity source password.
 

Device Registration and User or Device Changes

The following table summarizes how RSA SecurID Access handles device registration with user or device changes.

                      
Situation How RSA SecurID Access Handles It
A user completes device registration, deletes or uninstalls the RSA SecurID Authenticate app, and then later needs to complete device registration again on the same device. The user installs the RSA SecurID Authenticate app again and re-registers the device without administrative action.
 
  • A user completes device registration on one device and then gets a new device. The user needs to complete device registration on the new device.
  • A user performs a factory reset on a registered device and wants to reinstall the app on the same device.

The administrator must delete the user's current device before the user can complete device registration on the new device.

 
  • An existing user who has completed device registration on the device no longer needs the device and gives the device to a new user.
  • An existing user who has completed device registration on the device no longer needs the device, performs a factory reset, and gives the device to a new user.
 
  1. If necessary, the existing user deletes the RSA SecurID Authenticate app.
  2. The new user installs the app and completes device registration without administrative action.
 

Device Registration with Multiple Companies

An individual user can use the RSA SecurID Authenticate app on a single registered device to authenticate to resources protected by up to five different companies.

For example, a user who is a contractor for both Company A and Company B can use a single device to perform step-up authentication to access both companies. The user registers the device for one company and uses the My Account screen to add additional companies as needed.

An administrator might use a single device for testing the behavior of the RSA SecurID Authenticate app for a company's testing environment and production environment. In this case, each environment has a unique company ID that the administrator uses when registering the device with each environment.

If an administrator for one company uses the Cloud Administration Console to delete a user's registered device, the RSA SecurID Authenticate app on the user's device continues to work normally for any other companies. The activity from one company does not affect the app behavior for other companies.

 

 

You are here
Table of Contents > Users and Devices > Device Registration

Attachments

    Outcomes