Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

[Okta Verify] Failed to register for Push Authent

  • /e/ version: e-0.7-n-2019122535327-dev-serranoltexx
  • Device model: serranoltexx
  • When it started to occur: at first try
  • Reproducible with the last /e/ version: using the last version
  • Reproducible with LineageOS: did not try

Summary

Okta Verify application fails to authenticate through QRCode scanning. /!\ Failed to register for Push Authent message is displayed.

  • The device is unusable
  • The bug is the source of a data loss or a big waste of time
  • The bug concerns a third-party application
  • The bug concerns security
  • The bug concerns privacy

The problem

  • Install Okta Verify
  • Run Okta Verify
  • Scan an authentication QR Code

What is the current behavior?

/!\ Failed to register for Push Authent message is displayed.

What is the expected correct behavior?

The authentication should run fine.

Technical informations

https://zerobin.net/?f6372b8ef0345541#lcOibxj/2wnJx4LFI7p4/nh4AlphzMxnn4rNq3eFO6w=

The interesting part being here:

793 29806 D GmsMeasureBrokerSvc: bound by: GetServiceRequest{serviceId=MEASUREMENT, gmsVersion=12451000, packageName='com.okta.android.auth', extras=Bundle[{}]}
516  4516 I EnrollmentActivity: Received scanner result
516  4516 I EnrollmentActivity: Analyzing QR scanner results
516  4516 I URIResult: QRCode contains valid API registration data
516  4516 I EnrollmentActivity: Waiting for enrollment callback
793 29808 D GmsMeasureSvcImpl: onTransact [unknown]: 10, android.os.Parcel@9d6505d, 16
793 29806 D GmsMeasureSvcImpl: onTransact [unknown]: 10, android.os.Parcel@1aabdd2, 16
602   661 D Sensors : LightSensor readEvents x = 10.000000, raw = 10
516  4665 I GcmIntentService: Registering device with server
793 29793 D GmsGcmRegisterSvc: onBind: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms }
516  4516 W RegistrationProcessor: Token retrieval failed.
516  4516 W RegistrationProcessor: Error: SERVICE_NOT_AVAILABLE
516  4665 E RegistrationProcessor: Error registering device with FCM, no registration id received

Tried with/without Privacy Guard, and also on a Guest account: same result.

Relevant screenshots

Okta won't allow screenshot application to work fine. A black screenshot is generated. But basically, you get to the Okta verify home screen, with a "redish" alert ribbon on the bottom indicating /!\ Failed to register for Push Authent.

Solutions

None yet.

Possible fixes

It might be linked to the application trying to launch a service that fails.

Edited by n