Authenticate with Q&A Profile
Use this activity to authenticate a user with a personal Questions and Answers profile. In this activity you can specify mandatory and helpdesk questions from user’s Q&A profile that a user must answer to be authenticated.
IMPORTANT: If the questions you selected in this activity are not found in the user’s Q&A profile, the user will not be authenticated and the workflow containing this activity will not be performed for this user.
You can select one of the following authentication methods:
-
Answers to the specified questions (user’s answer is shown): In this mode, a helpdesk operator will ask a user for complete answers to the specified questions, and then compare them to the answers displayed on the identity verification page.
IMPORTANT: This option cannot be used if user answers to mandatory questions are not stored using reversible encryption. To store answers using reversible encryption, select the corresponding option in the Q&A profile settings. For more information, see Configuring Q&A Profile Settings.
-
Answers to the specified questions (user’s answer not shown): In this mode, a helpdesk operator will ask a user for complete answers to the specified questions, and enter the answers on the identity verification page.
-
Random characters of answers to the specified questions: In this mode, a helpdesk operator will ask a user to tell the specified number of characters in the user's answer to a specified question, and then type in those characters in the appropriate positions on the identity verification page.
Authenticate via Phone
Use this activity to include phone-based authentication in a helpdesk workflow. If your license includes phone-based authentication service, you will be able to configure and use this activity.
If your license does not include phone-based authentication service and you want to use this service, you can access the Support Portal at https://support.oneidentity.com/.
Before enabling the phone-based authentication, make sure that the users’ phone numbers that are stored in AD LDS are in the correct format. The phone number must meet the following requirements:
-
The number starts with either 00 or + followed by a country code and subscriber’s number. For example, +1 555-789-1314 or 00 1 5554567890.
-
The number can have extensions. For example, the number +1 555 123-45-67 ext 890.
-
Digits within the number can be separated by a space, hyphen, comma, period, plus and minus signs, slash (/), backward slash (\), asterisk (*), hash (#), and a tab character.
-
The number can contain the following brackets: parentheses (), curly braces {}, square brackets [], and angle brackets <>. Only one set of brackets is allowed within the number. The opening bracket must be in the first half of the number. For example, the number +15551234(567) will be considered invalid.
The USA numbers may not start with 00 or + sign, if they comply with all other requirements and contain 11 digits. For example, the number 1-555-123-3245 will be considered valid.
This activity has the following settings:
-
Authentication method: You can specify whether you want users to receive a call or an SMS with a one-time PIN code by selecting a corresponding option. You can also allow helpdesk operators to offer users to choose the authentication method by selecting the Allow users to choose between an automated voice call and SMS option.
-
SMS template: Enter the text message that will contain a one-time PIN code and will be sent to users during phone authentication.
-
telephoneNumber, homePhone, mobile and other attributes: Select one or several attributes of a user account from which telephone numbers will be used during phone-based authentication. You can also specify other attributes.
You can test the configured settings by clicking the Test settings button and entering the phone number to which a one-time PIN code will be sent.
Authenticate with Defender
IMPORTANT:
-
Authenticating with Defender is an activity not supported with the current release of Password Manager ADLDS.
-
Change or Reset password in Active Directory and connected systems is not supported in ADLDS.
You can use this activity to configure Password Manager to use Defender to authenticate users.
Defender is a two-factor authentication solution that authenticates users without forcing them to remember another new password. Defender uses one-time passwords (OTP) generated by special hardware or software tokens. Even if an attacker captures the password, there will be no security violation, since the password is valid only for one-time-use and can never be re-used.
You can use the Defender authentication to authenticate users before resetting their passwords or unlocking their Q&A profiles.
Before configuring the settings in this activity, install and configure Defender as described in the Defender documentation.
IMPORTANT: To make Password Manager use the Defender authentication, you must install the Defender Client SDK on the server on which Password Manager Service is installed.
This activity has the following settings:
-
Defender Server (IP address or DNS name): Specify Defender Server IP address or DNS name.
-
Port number: Type the port number that the Defender Access Node uses to establish a connection with the Defender Server.
-
Server timeout: Specify Defender Server time-out (in minutes).
-
Defender shared secret: Provide the secret that the Defender Access Node will share when it attempts to establish a connection with the Defender Server.
Authenticate with RADIUS Two-Factor Authentication
Use this activity to configure Password Manager to use a RADIUS server for two-factor authentication.
It uses one-time passwords (OTP) generated by hardware or software tokens for authentication.
You can use RADIUS Two-Factor Authentication to authenticate users before allowing them to reset or change their passwords, to unlock accounts, or manage Questions and Answers profiles.
Before using RADIUS Two-Factor Authentication for authentication, users have to configure it in General Settings tab on the home page of the Administration Site. For more information, see RADIUS Two-Factor Authentication.
