Challenge Processor Challenge Type

Implementing OTP Anywhere 11-5 The UMS OTP implementation is integrated into the OAAM Server login, challenge, and registration flows using the OAAM Server challenge processor framework. For information on the login, challenge, and registration flows, refer to Chapter 2, Natively Integrating with Oracle Adaptive Access Manager.

11.5 Configuring OTP

This section contains the following topics: ■ Integrating UMS ■ Enabling OTP Challenge Types ■ Enabling Registration and User Preferences

11.5.1 Integrating UMS

The properties to set for the UMS server URLs and credentials are listed below. They can be edited using the Property Editor in OAAM Admin. Note: End point is the Web Services URL that OAAM uses to send calls into UMS. Task 6 - Set up registration and challenge page messaging Customize the messaging that appear on the registration and challenge pages. Task 7 - Customize OTP message text. Customize the message containing the One Time Password Task 8 - Register Processors 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. Task 9 - Configure challenge pads for challenge types. Specify the type of device to use based on the purpose of the device. Table 11–3 UMS Server URLs and Credentials Property Default Value Description bharosa.uio.default.ums.integration.webservice UMS Server Webservice URL http:UMS Server URL:UMS Portucsmessagingwebservice bharosa.uio.default.ums.integration.parlayx.endpoint UMS Server ParlayX Endpoint URL http:UMS Server URL:UMS PortsdpmessagingparlayxSendMe ssageService bharosa.uio.default.ums.integration.useParlayX false Configures the use of webservice or parlayx API. The value is false by default Webservices recommended bharosa.uio.default.ums.integration.userName Username for UMS server bharosa.uio.default.ums.integration.password Password for UMS server bharosa.uio.default.ums.integtaion.policies UMS authentication policies bharosa.uio.default.ums.integration.fromAddress demooracle.com OAAM from address for OTP messages bharosa.uio.default.ums.integration.message.status.poll.attempts 3 Number of times to attempt status poll each time the wait page is displayed Table 11–2 Cont. Tasks in the OTP Setup Task Description 11-6 Oracle Fusion Middleware Developers Guide for Oracle Adaptive Access Manager After you set up the UMS server properties, restart the application.

11.5.2 Enabling OTP Challenge Types

Enable challenge types by setting the appropriate property to true. By setting the property to true, policies will be able to challenge using OTP via the challenge type email, SMS, IM, or Voice. The user will see the email, SMS, IM, or Voice page in registration flow. 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.

11.5.3 Enabling Registration and User Preferences

Enable the registration flow and user preferences by setting these properties to true:

11.6 Customizing OTP

This section contains the following topics: ■ Customizing Registration Fields and Validations bharosa.uio.default.ums.integration.message.status.poll.delay 1000 Delay between status polls while the wait page is being displayed bharosa.uio.default.ums.integration.sleepInterval 10000 bharosa.uio.default.ums.integration.deliveryPage.delay 3000 Table 11–4 UMS OTP challenge types Property Default Value Description bharosa.uio.default.challenge.type.enum.ChallengeEmail.available false Availability flag for email challenge type bharosa.uio.default.challenge.type.enum.ChallengeSMS.available false Availability flag for SMS challenge type bharosa.uio.default.challenge.type.enum.ChallengeIM.available false Availability flag for instant message challenge type bharosa.uio.default.challenge.type.enum.ChallengeVoice.available false Availability flag for voice challenge type Table 11–5 Enable OTP Profile Registration and Preference Setting Property Description bharosa.uio.default.register.userinfo.enabled Setting the property to true enables the profile registration pages if the OTP channel is enabled and requires registration. bharosa.uio.default.userpreferences.userinfo.enabled Setting the property to true enables the user to set preferences if the OTP channel is enabled and allows preference setting. User Preferences is a page that allows the user to change their imagephrase, challenge questions, un-register devices, and update their OTP profile. Table 11–3 Cont. UMS Server URLs and Credentials Property Default Value Description