Users complete device registration so that they can use the RSA SecurID Authenticate app (registered on a phone, tablet, or desktop or PC) or FIDO Token to authenticate to protected applications.
Device registration binds the device to the user. After device registration, when the user needs to authenticate to an application, RSA SecurID Access prompts the user for methods that the user can complete, for example, Approve, RSA SecurID Authenticate Tokencode, or Device Biometrics. Users who do not register a device using the RSA SecurID Authenticate app are not presented with authentication methods that require the app.
SMS Tokencode, Voice Tokencode, and RSA SecurID token do not require this type of registration.
A user can register a single device with the RSA SecurID Authenticate app installed.
For more information, see:
Users can register an iOS, Android, or Windows device using one of the following methods.
Use RSA SecurID Access My Page, a web portal that helps provide a secure way for users to register iOS, Android, or Windows devices using multifactor authentication and QR or numeric registration codes. Users sign into My Page on one device (for example, a computer), download the RSA SecurID Authenticate app on another device (iOS, Android, or Windows 10), scan a QR code, and complete an optional test authentication. Users can also manually enter a numeric registration code if they are unable to scan a QR code.
By default, My Page is disabled. You must enable it in Platform > My Page before users can use My Page. When you enable My Page, you also select the primary authentication method and the policy to use for additional authentication for signing into My Page.
Download the RSA SecurID Authenticate app on a device (iOS, Android, or Windows 10) and enter the identity source email address, your Company ID, and the identity source password (as the Registration Code) in the app.
You can use the Device Registration Using Password policy to restrict which users are allowed to complete device registration using an identity source password as a registration code. For more information, see Device Registration Using Password Policy.
For a complete overview of the steps users perform to complete device registration, see RSA SecurID Authenticate Device Registration Visual Overview. For rollout information, see Cloud Authentication Service Rollout to Users.
The following table summarizes how RSA SecurID Access handles device registration with user or device changes for iOS, Android, and Windows devices.
|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.|
| || |
The user can delete the current device in My Page , and then complete device registration. Or the administrator must delete the user's current device before the user can complete device registration again.
| || |
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 Accounts 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.
For FIDO Tokens, registration happens in one of two ways:
The first-time user clicks an icon for a protected application, enters an identity source password, inserts the FIDO Token, and, if required, taps the token. Subsequent authentications do not require a password. This is the default registration method.
The user goes to My Page to register the FIDO Token. Users authenticate to My Page according to the access policy protecting My Page. You can make My Page registration a requirement by enabling both My Page and FIDO Token registration in the Cloud Administration Console at Platform > My Page. After both functions are enabled, users can no longer register FIDO Tokens during first-time authentication.
During registration, the user enters an identity source password, inserts the FIDO Token, and, if required, taps the token. Subsequent authentications do not require a password. For a list of supported browsers for the FIDO Token, see Cloud Authentication Service User Requirements.
The following table summarizes how RSA SecurID Access handles device registration with user or device changes for FIDO Tokens.
|Situation||How RSA SecurID Access Handles It|
|A user registers a FIDO Token and then loses the token.||The administrator deletes the user's lost token from the Cloud Authentication Service, or the user deletes it using My Page. The administrator gives the user a new token to register.|
|A user registers a FIDO Token, no longer needs it, and gives it to another user.||The administrator deletes the user's token or the user deletes it using My Page. The new user must re-register the token.|