Joining Entity Data Tables and Transaction data tables

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 Developing Custom Challenge Processors 20-7

20.4.2 Set Contact Information Inputs

If user information registration and user preferences are true, configure input information. Contact information inputs are defined in userinfo.inputs.enum. The enum element is: bharosa.uio.application.userinfo.inputs.enum.inputname Email Input Example bharosa.uio.default.userinfo.inputs.enum.email=1 bharosa.uio.default.userinfo.inputs.enum.email.name=Email Address bharosa.uio.default.userinfo.inputs.enum.email.description=Email Address bharosa.uio.default.userinfo.inputs.enum.email.inputname=email bharosa.uio.default.userinfo.inputs.enum.email.inputtype=text bharosa.uio.default.userinfo.inputs.enum.email.maxlength=40 bharosa.uio.default.userinfo.inputs.enum.email.required=true bharosa.uio.default.userinfo.inputs.enum.email.order=2 bharosa.uio.default.userinfo.inputs.enum.email.enabled=true bharosa.uio.default.userinfo.inputs.enum.email.regex=.+[a-zA-Z_ ]+?\\.[a-zA-Z]{2,3} bharosa.uio.default.userinfo.inputs.enum.email.errorCode=otp.invalid.email bharosa.uio.default.userinfo.inputs.enum.email.managerClass=com.bharosa.uio.manage r.user.DefaultContactInfoManager

20.5 Configure the Challenge Pads Used for Challenge Types

By default, challenge devices that will be used are configured through rules. The rules are under the AuthentiPad checkpoint where you can specify the type of device to use based on the purpose of the device. To createupdate policies to use the challenge type: 1. Add a new rule action, MyChallenge, with the enum, rule.action.enum. Table 20–3 Properties for Contact Input Property Description inputname Name used for the input field in the HTML form inputtype Set for text or password input maxlength Maximum length of user input required Set if the field is required on the registration page order The order displayed in the user interface regex Regular expression used to validate user input for this field errorCode Error code used to look up validation error message bharosa.uio.application ID.error.errorCode managerClass java class that implements com.bharosa.uio.manager.user.UserDataManagerIntf if data is to be stored in Oracle Adaptive Access Manager database this property should be set to com.bharosa.uio.manager.user.DefaultContactInfoManager