OAA Push Notifications Fail When Sending to Android Devices After June 21, 2024
(Doc ID 3029206.1)
Last updated on JUNE 20, 2024
Applies to:
Oracle Advanced Authentication - Version 12.2.1.4 and later Information in this document applies to any platform.
Symptoms
When Using OAA to send second-factor push notifications to Android devices, the notifications are not received on the Android device and an error is found in the OAA push notification pod logs (oaainstall-push-zzzzz) and (oaainstall-spui-zzzz) when connecting to the Google push notification server at https://fcm.googleapis.com/fcm/send.
The end-user will not receive the push notification on their Android device and they may see a "System Error" or "Internal Error" in the browser with a failed login attempt or unable to connect to GCM Server. Too many failed attempts could result in the end-user account being locked.
Note: This issue does not affect timed-based one-time passwords (TOTP) on Apple or Android devices nor does it affect push notifications to Apple devices. This issue is specific to push notification on Android devices only.
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
