How to Configure OAM 11g for One-Time Passwords for Use with the Oracle Mobile Authenticator Application
(Doc ID 2307570.1)
Last updated on MAY 08, 2023
Applies to:
Oracle Access Manager - Version 11.1.2.3.0 to 11.1.2.3.0 [Release 11g]Oracle Mobile and Social - Version 11.1.2.3.0 to 11.1.2.3.0 [Release 11gR2]
Oracle Unified Directory - Version 11.1.2.3.0 to 11.1.2.3.0 [Release 11g]
Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.
Goal
How to configure OAM 11g for second factor authentication (SFA) allowing end-users to enter a one-time PIN (OTP) number displayed in the Oracle Mobile Authenticator (OMA) application on a mobile device.
The one-time PIN is time-based meaning that any specific PIN in only valid for a set amount of time. After that time period has expired then a new PIN is required to complete the SFA login step. The PIN is generated based off of a shared secret key that is known to both the OAM server and the OMA application.
The steps listed below should work correctly for both Android and iOS devices.
Important Notes:
- This note covers the time-based one-time PIN option only. While the configuration of push notifications with the OMA application covers some of the same pieces (such as OMA and the AdaptiveAuthentication scheme) the configuration is much more complex and not covered in this document.
- This document covers the setup of time-based one-time PIN (TOTP) with the OAM 11g server only. Very similar steps are needed to configure TOTP with the OAM 12c server but there are enough differences that a new note is warranted. The 12c configuration note is KM note 2503643.1.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| Configure the OAM server settings from within the OAM console |
| Create an authentication policy to protect a resource that contains a post-authentication rule to switch to the AdaptiveAuthentication scheme |
| Install the OMA application onto the mobile device |
| Create a webpage to deliver the OMA application profile to the mobile device |
| How to configure the OAM server to use a custom LDAP attribute to store the shared secret |
| Troubleshooting / Debugging |
| References |