Class Code Challenge Processors

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 20-8 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager 2. Create policy to return newly created action, MyChallenge, to use the challenge method. Alternatively, if you want to configure challenge devices using properties, you can bypass the AuthentiPad checkpoint by setting bharosa.uio.default.use.authentipad.checkpoint to false. Devices to use for the challenge type can be added. bharosa.uio.application.challengeType.authenticator.device=value The examples shown use the challenge type key, ChallengeEmail and ChallengeSMS to construct the property name. bharosa.uio.default.ChallengeSMS.authenticator.device=DevicePinPad bharosa.uio.default.ChallengeEmail.authenticator.device=DevicePinPad Available challenge device values are DeviceKeyPadFull, DeviceKeyPadAlpha, DeviceTextPad, DeviceQuestionPad, DevicePinPad, and DeviceHTMLControl. Table 20–4 Authentication Device Type Property Description None No HTML page or authentication pad DeviceKeyPadFull Challenge user using KeyPad. DeviceKeyPadAlpha Challenge user with the alphanumeric KeyPad numbers and letters only, no special characters DeviceTextPad Challenge user using TextPad. DeviceQuestionPad Challenge user using QuestionPad. DevicePinPad Challenge user using PinPad. DeviceHTMLControl Challenge user using HTML page instead of an authentication pad.