Best Practices: Bypassing Strong Authentication Questions During Registration

Best Practices: Bypassing Strong Authentication Questions During Registration

Overview

As part of the initial account claiming process with IdentityNow, users are sometimes asked to provide some registration information to help verify who they are when attempting things such as recovering forgotten passwords. This is part of the "strong authentication" configuration that IdentityNow administrators can set up for a given identity profile:

 

StrongAuthOptions_1.png

Note that for both the Password Reset/User Unlock and Strong Authentication methods, at least one option must be selected.

While useful, this configuration can sometimes lead to confusion for end users, especially if their organization already leverages strong authentication elsewhere. Many Identity Providers already collect this information, and organizations who are using those providers to single sign-on (SSO) into IdentityNow actually do no need to leverage strong authentication with IdentityNow too.

 

Bypassing Strong Authentication Questions

As an IdentityNow administrator, you can specify which methods of strong authentication are permissible per your organization's security policy using the configuration pictured above. What is important to understand is that, if an option is marked as available for a user to choose during the strong authentication process, and IdentityNow does not already have the necessary information to complete that action, the user will be prompted for that information at the time of initial sign-in.

For example, if "By answering a security question" is checked, and the user has not selected his/her security questions and answers, he/she will be prompted to supply those upon login. Alternatively, if "By providing a verification code sent to alternate email" is selected and the user's identity already has an alternate phone number populated, he/she will not be prompted to supply it.

If you want to suppress all prompts for user information because you are leveraging a combination of multi-factor authentication and SSO elsewhere, the best practice is to select only options where you know the identity attribute underlying that method will always be populated. Because IdentityNow requires that all identities have a work email, the simplest way to accomplish this is to simply select "By providing a verification code sent to work email" for both the Password Reset/User Unlock and Strong Authentication methods, as below:

StrongAuthOptions_2.png

This configuration will allow new users logging into IdentityNow to bypass registration questions, since the work email identity attribute will always be non-empty.

Version history
Revision #:
3 of 3
Last update:
‎Apr 24, 2021 10:54 AM
Updated by:
 
Contributors