MFA push stuck on loading page. (Android and Chrome)

Help
1

Hello,

we are experiencing a problem with our MFA wants to send a push notification.
It’s stuck on the loading page and sometimes a browser refresh is producing your ‘missing client parameter’ error in the Auth0 log.

We’ve narrowed it down to a combination of an Android OS and the google Chrome browser.
Any onter combination works fine. No errors and no problems login in.

Cheers,
Dennis

3

Hi,

Any updates on this issue?

Some of our customers (Chrome web-browser on Android device) can not login at the moment, which is really problematic. As we’ve mentioned in other issues: we are using the auth0 hosted pages, and have set back all the layout modifications. We have also verified that the /authorize endpoint is being used by the hosted login page.

The username-password login is working, but when a user should receive a SMS or push notification (MFA) the page is stuck on the loading screen (see below):

stuck

Our log doesn’t show any errors either. On a success login the following log-records are generated:

  1. Second factor started - Guardian - Start second factor authentication
  2. Push notification sent - Guardian - Second factor send push notification
  3. OTP Auth suceed - Guardian - Second factor authentication succeed
  4. Success Login

But when the page is stuck on the loading screen only the following log-record is generated:
1) Second factor started - Guardian - Start second factor authentication

… nothing else…

Any update or help is appreciated. Thanks.

4

This should have been resolved with the fix rolled out here

Are you still experiencing this?

6

Hi Jeremy,

Looks like it’s fixed now. Thanks for your time!

1 Like