Phone Input Additional Registration Field Definitions Examples

11-18 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager

11.10.3.1 Register Email Challenge Processor

The properties to register the email challenge processor and mark service as available or unavailable are listed below.

11.10.3.2 Register IM Challenge Processor

The properties to register the IM challenge processor and mark service as available or unavailable are listed below. Table 11–25 Challenge type enums Property Description available if the challenge type is available for use service ready and configured. To enabledisable an OTP challenge type, the available flag should be set. processor java class for handling challenges of this type. requiredInfo comma separated list of inputs from the registration input enum Table 11–26 Properties to register the email challenge processor 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 bharosa.uio.default.challenge.type.enum.ChallengeEmail.requiredInfo email Required fields to challenge user with email challenge type bharosa.uio.default.challenge.type.enum.ChallengeEmail.available false Availability flag for email challenge type bharosa.uio.default.challenge.type.enum.ChallengeEmail.otp true OTP flag for email challenge type Table 11–27 Properties to register the IM challenge processor Property Default Value Description bharosa.uio.default.challenge.type.enum.ChallengeIM 3 Instant message Challenge enum value bharosa.uio.default.challenge.type.enum.ChallengeIM.name IM Challenge Name of instant message challenge type bharosa.uio.default.challenge.type.enum.ChallengeIM.description Instant Message Challenge Description of instant message challenge type bharosa.uio.default.challenge.type.enum.ChallengeIM.processor com.bharosa.uio.proces sor.challenge.Challeng eIMProcessor Processor class for instant message challenge type bharosa.uio.default.challenge.type.enum.ChallengeIM.requiredInfo mobile Required fields to challenge user with instant message challenge type bharosa.uio.default.challenge.type.enum.ChallengeIM.available false Availability flag for instant message challenge type bharosa.uio.default.challenge.type.enum.ChallengeIM.otp true OTP flag for instant message challenge type Implementing OTP Anywhere 11-19

11.10.3.3 Register Voice Challenge Processor

The properties to register the Voice challenge processor and mark service as available or unavailable are listed below.

11.11 Challenge Use Case

An example challenge scenario is presented below. 1. Oracle Adaptive Access Manager Server presents the user with the user name page. 2. The user submits his user name on the user name page. 3. Oracle Adaptive Access Manager fingerprints the user device and runs pre-authentication rules to determine if the user should be allowed to proceed to the password page. 4. The user is allowed to proceed to the password page and he enters his password. 5. The OAAM policies indicate that the user should be challenged. 6. The challenge checkpoint is run to determine the type of challenge to use KBA, Email, SMS, and so on. If SMS challenge is returned, the SMS Challenge Processor is loaded and used to generate and deliver an OTP to the user via SMS. 7. Once the SMS has been sent, the user is presented with a challenge page indicating that his OTP has been sent to him in an SMS. 8. User submits correct OTP to continue into application and complete the login flow. The OTP generated and sent to the user is only valid for one correct submission within a single HTTP session. If the users HTTP session expires and a new OTP will be generated and sent if he is challenged again in a later session. Table 11–28 Properties to register the Voice challenge processor Property Default Value Description bharosa.uio.default.challenge.type.enum.ChallengeVoice 4 Voice Challenge enum value bharosa.uio.default.challenge.type.enum.ChallengeVoice.name Voice Challenge Name of voice challenge type bharosa.uio.default.challenge.type.enum.ChallengeVoice.description Voice Challenge Description of voice challenge type bharosa.uio.default.challenge.type.enum.ChallengeVoice.processor com.bharosa.uio.proces sor.challenge.Challeng eVoiceProcessor Processor class for voice challenge type bharosa.uio.default.challenge.type.enum.ChallengeVoice.requiredInfo phone Required fields to challenge user with voice challenge type bharosa.uio.default.challenge.type.enum.ChallengeVoice.available false Availability flag for voice challenge type bharosa.uio.default.challenge.type.enum.ChallengeVoice.otp true OTP flag for voice challenge type