Missing client parameter

[jaliperti1]

@jerdog

This isn’t an outage, but is instead around making sure everyone is using secure clients and best practice. Clients need to be utilizing the /authorize endpoint properly, and in turn will be logged in properly. The /login endpoint is not a documented part of our API and should not be used. The proper process is identified h

I am using the authorize endpoint using a Hosted Login page and still got this error for one customers this morning.

[jaliperti1]

Still having an issue, but it looks like the error message has changed to:

“You may have pressed the back button, refreshed during login, opened too many login dialogs, or there is some issue with cookies, since we couldn’t find your session. Try logging in again from the application and if the problem persists please contact the administrator.”

[denis]

Same problem here, i’m using lock hosted page (11.3.1)

Any update on this error?

[Dennis1]

Hi Jeremy,

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 earlier: 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):

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.

[Dennis1]

We’ve just noticed that it’s working correctly on Android 63.xxx, but fails after upgrading to Android 64.xxx or Android 65.xxx. It seems to be fixed in Android version 66.xxx.

[jerdog]

A fix was deployed to our preview and staging environments over the weekend and will be reaching production soon

[jerdog]

Just checking to see if this is still persisting?

[jerdog]

The fix rolls back to the previous login type of link where the query string parameters are there in the URL. However, end users that already bookmarked the old link will have it fail. Eventually errors will decrease

[tflight]

Seems to be fixed, thanks!