Setup Overview Setting Up OTP Anywhere

9-8 Oracle Fusion Middleware Administrators Guide for Oracle Adaptive Access Manager After you set up the UMS server properties, restart the application.

9.5.4 Enabling and Defining the OTP Challenge

The challenge type is the channel that OTP can use to challenge the user, such as Email, SMS, IM, and so on. The challenge type properties are used to associate a Challenge Type with a Challenge Processor, the java code needed to perform any work for challenges. Enable the OTP challenge type you want to use to challenge the user if secondary authentication is required by setting the available flag. Set bharosa.uio.default.challenge.type.enum.ChallengeSMS.available to true. Then, you can define the properties for the OTP challenge type, such as the required field for registration, and register the challenge processor that is handling the challenge processing. To enable and define a challenge type, such as ChallengeEmail, ChallengeSMS, ChallengeQuestion, and so on, perform the following steps: 1. Log in to OAAM Admin.

2. In the Navigation tree, double-click Properties under the Environment node. The

Properties Search page is displayed. 3. Search for bharosa.uio.default.challenge.type.enum and edit the properties for the out-of-the-box OTP challenge type: SMS Challenge Type The following is an example of an enum defining SMS challenge for OTP: Table 9–6 Properties for SMS Challenge Type Property Default Value Description bharosa.uio.default.challenge.type.enum.ChallengeSMS 2 SMS Challenge enum value bharosa.uio.default.challenge.type.enum.ChallengeSMS.name SMS Challenge Name of SMS challenge type bharosa.uio.default.challenge.type.enum.ChallengeSMS.description SMS Challenge Description of SMS challenge type bharosa.uio.default.challenge.type.enum.ChallengeSMS.processor com.bharosa.uio.proces sor.challenge.Challeng eSMSProcessor Processor class for SMS challenge type Specifies the java class for handling challenges of this type. The challenge mechanism is customizable through Java classes. See the Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager for information. Setting Up OTP Anywhere 9-9 Email Challenge Type The following is an example of the enum defining the challenge type, email challenge, for OTP: bharosa.uio.default.challenge.type.enum.ChallengeSMS.requiredInfo mobile Required fields to challenge user with SMS challenge type A comma separated list of inputs from registration input enum bharosa.uio.default.challenge.type.enum.ChallengeSMS.available false Availability flag for SMS challenge type Specifies if the challenge type is available for use service ready and configured. To enabledisable an OTP challenge type, the available flag should be set. bharosa.uio.default.challenge.type.enum.ChallengeSMS.otp true OTP flag for SMS challenge type Table 9–7 Properties for Email Channel Type Property Default Value Description bharosa.uio.default.challenge.type.enum.ChallengeEmail 1 Email Challenge enum value bharosa.uio.default.challenge.type.enum.ChallengeEmail.name Email Challenge Name of email challenge type bharosa.uio.default.challenge.type.enum.ChallengeEmail.description Email Challenge Description of email challenge type bharosa.uio.default.challenge.type.enum.ChallengeEmail.processor com.bharosa.uio.proces sor.challenge.Challeng eEmailProcessor Processor class for email challenge type Specifies the java class for handling challenges of this type. The challenge mechanism is customizable through Java classes. See the Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager for information. bharosa.uio.default.challenge.type.enum.ChallengeEmail.requiredInfo email Required fields to challenge user with email challenge type A comma separated list of inputs from registration input enum bharosa.uio.default.challenge.type.enum.ChallengeEmail.available false Availability flag for email challenge type Specifies if the challenge type is available for use service ready and configured. To enabledisable an OTP challenge type, the available flag should be set. bharosa.uio.default.challenge.type.enum.ChallengeEmail.otp true OTP flag for email challenge type Table 9–6 Cont. Properties for SMS Challenge Type Property Default Value Description