Customizing Registration Fields and Validations

11-10 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager bharosa.uio.default.userpreferences.userinfo.decline.enabled = true When the Decline button is enabled, the user will have another option on the OTP registration page that will allow him to Opt out of OTP challenges. He will not be asked to register OTP again, and will not receive OTP challenges. However, if a Customer Care OTP Profile reset is performed or reset all the user will have the opportunity to register OTP again. Also, even if the user has opted out of OTP, he can access the OTP page in User Preferences and add information and click Continue. This will remove the OTP out flag and the user will now be registered for OTP.

11.6.4 Customizing Challenge Page Messaging

Add challenge type fields to client_resource.properties.

11.6.5 Customizing OTP Message Text

Add OTP message fields to client_resource.properties.

11.6.6 Enabling Opt Out Functionality

This feature is disabled by default. To enable Opt Out for the user, set the property to true. Note: Even if these are true, the button will not show if the Opt Out property is false. Table 11–12 Challenge Type Resource Bundle Items Property Default Value bharosa.uio.default.ChallengeSMS.message For your protection please enter the code we just sent to your mobile telephone. If you did not receive a code please ensure that text messaging is enabled on your phone and click the resend link below. bharosa.uio.default.ChallengeSMS.registerdevice.message Check to register the device that you are currently using as a safe device: bharosa.uio.default.ChallengeSMS.continue.button Continue Table 11–13 Challenge Type Resource Bundle Items Property Default Value bharosa.uio.default.ChallengeSMS.incorrect.message Incorrect OTP. Please try again. bharosa.uio.default.ChallengeSMS.message.subject Oracle OTP Code bharosa.uio.default.ChallengeSMS.message.body Your Oracle SMS OTP Code is: {0} Table 11–14 OTP opt-out properties Property Default Value bharosa.uio.default.otp.optOut.enabled false bharosa.uio.default.otp.optOut.managerClass com.bharosa.uio.manager.user.DefaultContactInfoManager Implementing OTP Anywhere 11-11

11.7 Registering SMS Processor to Perform Work for Challenge Type

The challenge type enum is used to associate a Challenge Type with the java code needed to perform any work related to that challenge type. The Challenge Type ID ChallengeEmail should match a rule action returned by the rules when that challenge type is going to be used. Channel normally refers to the delivery channel used to send an OTP to the user Email, SMS, or IM. The properties to register the SMS challenge processor and mark service as available or unavailable are listed below.

11.8 Configuring 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.

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. Table 11–15 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–16 Properties to register the SMS challenge processor Property Default Value Description bharosa.uio.default.challenge.type.enum.ChallengeSMS 2 SMS Challenge enum value bharosa.uio.default.challenge.type.enum.ChallengeSMS.name SMS Challenge Name of SMS challenge type bharosa.uio.default.challenge.type.enum.ChallengeSMS.description SMS Challenge Description of SMS challenge type bharosa.uio.default.challenge.type.enum.ChallengeSMS.processor com.bharosa.uio.proces sor.challenge.Challeng eSMSProcessor Processor class for SMS challenge type bharosa.uio.default.challenge.type.enum.ChallengeSMS.requiredInfo mobile Required fields to challenge user with SMS challenge type bharosa.uio.default.challenge.type.enum.ChallengeSMS.available false Availability flag for SMS challenge type bharosa.uio.default.challenge.type.enum.ChallengeSMS.otp true OTP flag for SMS challenge type