Build Transaction Data SQL Queries and Views

Developing Custom Challenge Processors 20-5 implementing an email challenge processor is shown in Section 20.2.3, Example: Email Challenge Processor Implementation. The Challenge Type ID for example, ChallengeEmail should match a rule action returned by the rules when that challenge type is used. The rule action for ChallengeEmail is rule.action.enum.ChallengeEmail. The rule action is to challenge the user using email using the email delivery channel. Channel normally refers to the delivery channel used to send to the user.

20.3.2 Example: Defining an OTP Channel Type

To define a challenge type, use the following property: bharosa.uio.default.challenge.type.enum.MyChallenge In the property, default is the UIO application name, and MyChallenge is the Challenge Type being added. For example, ChallengeEmail is the Challenge Type in the example below. bharosa.uio.default.challenge.type.enum.ChallengeEmail The rule action is to challenge the user with email using the email delivery channel. rule.action.enum.ChallengeEmail To enabledisable a challenge type, the available flag should be set: bharosa.uio.default.challenge.type.enum.MyChallenge.available = false Setting the available flag and setting the enabled flag are different. The enabled flag would remove it from list. Example for Defining a Channel Type Attributes bharosa.uio.default.challenge.type.enum with example values are shown as follows: bharosa.uio.default.challenge.type.enum.MyChallenge = 1 unique value to identify Challenge Email in bharosa.uio.default.challenge.type.enum bharosa.uio.default.challenge.type.enum.MyChallenge.name = MyChallenge unique string to identify Challenge Email in bharosa.uio.default.challenge.type.enum, no spaces bharosa.uio.default.challenge.type.enum.MyChallenge.description = Email Challenge descriptive name bharosa.uio.default.challenge.type.enum.MyChallenge.processor = oracle.oaam.challenge.processor.challenge.EmailChallengeProcessor Processor used for sending emails instance of com.bharosa.uio.processor.challenge.ChallengeProcessorIntf Table 20–2 Challenge type Flags 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 20-6 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager bharosa.uio.default.challenge.type.enum.MyChallenge.requiredInfo = email comma separated field names, User registration flow captures these data fields, check Contact information Inputs section to define this enum bharosa.uio.default.challenge.type.enum.MyChallenge.available = false to turn off this service bharosa.uio.default.challenge.type.enum.MyChallenge.otp = true indicates this challenge is used for OTP, set it to true Email Example bharosa.uio.default.challenge.type.enum.ChallengeEmail = 1 bharosa.uio.default.challenge.type.enum.ChallengeEmail.name = Email Challenge bharosa.uio.default.challenge.type.enum.ChallengeEmail.description = Email Challenge bharosa.uio.default.challenge.type.enum.ChallengeEmail.processor = com.bharosa.uio.processor.challenge.EmailChallengeProcessor bharosa.uio.default.challenge.type.enum.ChallengeEmail.requiredInfo = mobile bharosa.uio.default.challenge.type.enum.ChallengeEmail.available = true bharosa.uio.default.challenge.type.enum.ChallengeEmail.enabled = true SMS Example bharosa.uio.default.challenge.type.enum.ChallengeSMS = 2 bharosa.uio.default.challenge.type.enum.ChallengeSMS.name = SMS Challenge bharosa.uio.default.challenge.type.enum.ChallengeSMS.description = SMS Challenge bharosa.uio.default.challenge.type.enum.ChallengeSMS.processor = com.bharosa.uio.processor.challenge.SmsChallengeProcessor bharosa.uio.default.challenge.type.enum.ChallengeSMS.requiredInfo = mobile bharosa.uio.default.challenge.type.enum.ChallengeSMS.available = true bharosa.uio.default.challenge.type.enum.ChallengeSMS.enabled = true

20.4 Configure User Input Properties

Instructions to configure user information properties are in the following sections: ■ Enable Registration and Preferences Input ■ Set Contact Information Inputs For instructions on customizing, extending, or overriding Oracle Adaptive Access Manager properties, refer to Chapter 7, Customizing Oracle Adaptive Access Manager.

20.4.1 Enable Registration and Preferences Input

Default configurations for enabling for registration and preference input are listed as follows: Contact information registration bharosa.uio.default.register.userinfo.enabled=false Contact information preferences bharosa.uio.default.userpreferences.userinfo.enabled=false