About the Implementation Oracle Fusion Middleware Online Documentation Library

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

11.4 OTP Setup Overview

OTP using UMS as a delivery method is a standard feature of the OAAM Server. This section contains an overview of the steps required to implement the feature. Follow the instructions for customizing the OAAM server interface through adding customized jars and files to an extensions shared library. For information, refer to Chapter 7, Customizing Oracle Adaptive Access Manager. . Table 11–1 Connecting to the Vendor Parameter Description SmsAccountId The Account Identifier on the SMS-C. This is your vendor account ID which you need to get from the vendor. SmsServerHost The name or IP address of the SMS-C server. TransmitterSystemId TransmitterSystemPassword The password of the transmitter system. This includes Type of Password choose from Indirect PasswordCreate New User, Indirect PasswordUse Existing User, and Use Cleartext Password and Password. This is the password corresponding to your vendor account ID TransmitterSystemType The type of transmitter system. The default is Logica. ReceiverSystemId The account ID that is used to receive messages. ReceiverSystemPassword ReceiverSystemType The type of receiver system. The default is Logica. ServerTransmitterPort The TCP port number of the transmitter server. ServerReceiverPort The TCP port number of the receiver server. DefaultEncoding The default encoding of the SMPP driver. The default is IA5. Choose from the drop-down list: IA5, UCS2, and GSM_DEFAULT. DefaultSenderAddress Default sender address Table 11–2 Tasks in the OTP Setup Task Description Configure Configuration involves Tasks 1 through 3. OTP Challenge is not enabled by default. It has to be enabled by setting these properties. Task 1- Integrate UMS. Set up UMS URLs and credentials so that OAAM can communicate with the UMS server. Task 2 - Make Challenge Types available. Make it possible for the policies to challenge using OTP via the challenge type. Task 3 - Enable Registration and User Preferences. Enable registration and user preferences. The user will use the pages for profile registration and resetting OTP profile. Customize Customizations involves Tasks 4 through 7. Task 4 - Set up the user registration fields and validations. Set up the registration and preferences page input fields for the user. Input properties includes maximum length for the email address the user can enter, validation for the email address field expression, and so on. Note: Any user facing strings will need to be duplicated into resource bundle. Task 5 - Set up Terms and Condition fields. Additional fields to set up are Terms of Service, Privacy Policy, and so on. 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