Configuring OAA Properties for Android Push Notification using Legacy FCM APIs

F.2 Configuring OAA Properties for Android Push Notification using Legacy FCM APIs

You must set up some OAA properties that are required for configuring push notifications for Android devices.

The following table lists the OAA properties that you can configure for push notification for Android.

Table F-1 OAA Properties

Property Name	Description	Sample Value
bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.proxyProtocol	The protocol of the proxy server.	http or https
bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.proxyHost	The host name or IP address of the proxy server.	proxy.example.com
bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.proxyPort	The port of the proxy server.	80
bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.pushPreferencesEndpoint	The host and port used for push factor registration. This host and port should be accessible from the device. This corresponds to the host and port referenced in the SpuiUrl (`SpuiUrl=https://<host:port>/oaa/rui`) in Printing Deployment Details.	https://oaainstall
bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.challengeAnswerEndpoint	The host and port used for push factor runtime. This host and port should be accessible from the device. This corresponds to the host and port referenced in the Push URL (`Push=https://<host:port>/oaa-push-factor`) in Printing Deployment Details.	https://oaainstall
bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.retrycount	Maximum number of unsuccessful retries of the challenge. Beyond this count the challenge is locked. The default value is 10. If you are using push notifications with Oracle Universal Authenticator you must set this value to 50.	50
bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.google.firebase.serverKey	The Firebase Server Key. See Creating a Google Firebase Project Enabled for Google Cloud Messaging Using Legacy FCM APIs.	AAAAh1hlXa8:APA91....
bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.google.firebase.senderId	The Firebase Sender ID. See Creating a Google Firebase Project Enabled for Google Cloud Messaging Using Legacy FCM APIs.	58213467743

Note:

The proxyProtocol, proxyHost, and proxyPort properties are only required if internet access is available through a proxy server. If OAA has direct access to the internet these properties do not need to be set.

You can configure the OAA properties using the following REST API:

PUT  <PolicyUrl>/policy/config/property/v1

Note:

In this case remove /oaa-policy from the <PolicyUrl>, for example use https://<host>:<port>/policy/config/property/v1 not https://<host>:<port>/oaa-policy/policy/config/property/v1

Consider the following example of configuring an OAA property using the CURL command. The example below assumes OAA accesses the internet through a proxy server:

curl --location -g --request PUT 'https://<PolicyUrl>/policy/config/property/v1' \
--header 'Content-Type: application/json' \
--header 'Authorization: Basic <Base64Encoded(<username>:<password>)>' \
--data '[
{
"name": "bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.proxyProtocol",
"value": "https"
},
{
"name": "bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.proxyHost",
"value": "proxy.example.com"
},
{
"name": "bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.proxyPort",
"value": "80"
},
{
"name": "bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.pushPreferencesEndpoint",
"value": "https://oaainstall"
},
{
"name": "bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.challengeAnswerEndpoint",
"value": "https://oaainstall"
},
{
"name": "bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.retrycount",
"value": "50"
},
{
"name": "bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.google.firebase.serverKey",
"value": "AAAAh1hlXa8:APA91bGOGR4pMYe9GC6a2rU169hTCBVmc................................LpU2F8_Egn7IZguC1Rr2HSNnROzXu1d1Lam0TJ"
},
{
"name": "bharosa.uio.default.challenge.type.enum.ChallengeOMAPUSH.google.firebase.senderId",
"value": "58213467743"
}
]'

For details about finding the PolicyUrl and authenticating, see OAA Admin API.

For details about the REST API, see Configuration Properties REST Endpoints.

Next Steps: Registering the User Account with Oracle Mobile Authenticator for Android.