How to Configure Oracle Access Manager 12c (OAM 188.8.131.52) for One-Time Passwords for Use with the Oracle Mobile Authenticator Application
(Doc ID 2503643.1)
Last updated on NOVEMBER 07, 2023
Oracle Access Manager - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 12c] 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.
How to configure Oracle Access Manager 12c (OAM 18.104.22.168) 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.
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 theOAM 12g server only. Very similar steps are needed to configure TOTP with the OAM 11c server but there are enough differences that a new note is warranted. See Note: 2307570.1 for configuration of an OAM 11g server.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!