The following sections contain procedures for using OMA on an Android mobile device.
Copying a One-Time Password from the Oracle Mobile Authenticator on Android
Editing an Account on the Oracle Mobile Authenticator on Android
Deleting an Account on the Oracle Mobile Authenticator on Android
Responding to Access Request (Push) Notifications on Android
Displaying Access Request (Push) Notifications History on Android
This procedure configures the OMA on Android to communicate with Access Manager. A configuration URL is provided by the Access Manager administrator either by e-mail or through a web page. Details about the URL are in Understanding Oracle Mobile Authenticator Configuration.
The OMA must authenticate and register an account with Access Manager. Be sure to complete Configuring the Oracle Mobile Authenticator for Android before attempting these procedures. Any of the following procedures can be used to initialize the OMA.
Once authenticated, the app receives a key from the server that will be used to generate the OTP.
You can manually configure a OTP account by entering a unique account name and key. This is the same account that would be created automatically in Initializing the Oracle Mobile Authenticator for OTP Generation on Android.
The OMA must register successfully with the Google Cloud Messaging (Push Notification) servers and get a unique registration token. This registration token is sent to Access Manager to complete the push notification setup. Once complete, the OMA can register with Access Manager to receive push notifications.
The OMA must register successfully with the Google Cloud Messaging (Push Notification) Servers and get a unique registration token. This registration token is sent to Access Manager to complete the push notification setup. Afterwards, the OMA can register with Access Manager to receive push notifications.
The OMA can also be configured with a URL that contains the key used for generating a OTP. This allows for OTP generation when the mobile app is offline. This configuration URL contains the secret key so it should be delivered on a secure channel.
Use this procedure to copy a OTP from the OMA.
Use this procedure to edit an account on the OMA.
Use this procedure to delete an account on the OMA.
The OMA can receive push notifications from Access Manager if the push notification option is selected when configuring two factor authentication. An administrator can use this procedure to respond to the notifications received on the mobile device.
You can see the notifications which were received by the OMA and the decision taken for that particular access request.
You can display the services with which the OMA has been configured. This corresponds to the unique service name defined in Configuring the Oracle Mobile Authenticator for Android.
You can see all the accounts that are added to the OMA and check the account type (OTP, notification or a combination of both). This corresponds to accounts configured using one of the procedures in Initializing the Oracle Mobile Authenticator on Android.