Configuring the Challenge Pads Used for Challenge Types

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

11.9.3 Custom Implementation Recommendations

Extend the base implementation class DefaultContactInfoManager, and override the setUserDataValue and getUserDataValue methods to store the data values where appropriate for you implementation. Leave the default implementation of setUserDataFlag and getUserDataFlag in place in order for OAAM to properly track which data has been set for the user.

11.9.4 Configuring Properties

OTP Anywhere registration fields are defined by the user defined enum: bharosa.uio.default.userinfo.inputs.enum. Each element has a managerClass property that designates which class will be used to store the registration data. For example, the default mobile phone element is as follows: bharosa.uio.default.userinfo.inputs.enum=Enum for Contact information bharosa.uio.default.userinfo.inputs.enum.mobile=0 bharosa.uio.default.userinfo.inputs.enum.mobile.name=Mobile Phone bharosa.uio.default.userinfo.inputs.enum.mobile.description=Mobile Phone bharosa.uio.default.userinfo.inputs.enum.mobile.inputname=cellnumber bharosa.uio.default.userinfo.inputs.enum.mobile.inputtype=text bharosa.uio.default.userinfo.inputs.enum.mobile.maxlength=16 bharosa.uio.default.userinfo.inputs.enum.mobile.required=true bharosa.uio.default.userinfo.inputs.enum.mobile.order=4 bharosa.uio.default.userinfo.inputs.enum.mobile.enabled=true bharosa.uio.default.userinfo.inputs.enum.mobile.regex=\\d{1}\\D?\\d{3}\\D?\\D?\ \d{3}\\D?\\d{4} bharosa.uio.default.userinfo.inputs.enum.mobile.errorCode=otp.invalid.mobile bharosa.uio.default.userinfo.inputs.enum.mobile.managerClass=com.bharosa.uio.manag er.user.DefaultContactInfoManager As shown, the default mobile phone definition uses the DefaultContactInfoManager class to manage the data. If a custom implementation is desired, the value of the managerClass attribute can be updated in OAAM Admin or through OAAM Extension shared library to use a custom class.

11.10 Example Configurations

This section contains the following topics: ■ Additional Registration Field Definitions Examples ■ Additional Challenge Message Examples ■ Additional Processors Registration Examples

11.10.1 Additional Registration Field Definitions Examples

Additional registration field definitions are shown below. Implementing OTP Anywhere 11-15

11.10.1.1 Email Input

The following is an example of an enum defining email registration on the OTP registration page of an authenticator:

11.10.1.2 Phone Input

The following is an example of an enum defining phone registration on the OTP registration page of an authenticator: Table 11–18 Contact Information Inputs 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 Table 11–19 Email Input Property Default Value Description bharosa.uio.default.userinfo.inputs.enum.email 1 Email address enum value bharosa.uio.default.userinfo.inputs.enum.email.name Email Address Name for email address field bharosa.uio.default.userinfo.inputs.enum.email.description Email Address Description for email address field bharosa.uio.default.userinfo.inputs.enum.email.inputname email HTML input name for email address field bharosa.uio.default.userinfo.inputs.enum.email.inputtype text HTML input type for email address field bharosa.uio.default.userinfo.inputs.enum.email.maxlength 40 HTML input max length for email address field bharosa.uio.default.userinfo.inputs.enum.email.required true Required flag for email address field during registration and user preferences bharosa.uio.default.userinfo.inputs.enum.email.order 2 Order on the page for email address field bharosa.uio.default.userinfo.inputs.enum.email.enabled false Enabled flag for email address enum item bharosa.uio.default.userinfo.inputs.enum.email.regex .+[a-zA-Z_ ]+?\\.[a-zA-Z]{2,3} Regular expression for validation of email address field bharosa.uio.default.userinfo.inputs.enum.email.errorCode otp.invalid.email Error code to get error message from if validation of email address entry fails bharosa.uio.default.userinfo.inputs.enum.email.managerClass com.bharosa.uio.ma nager.user.DefaultC ontactInfoManager Java class to use to save retrieve email address from data storage