Auth0 Home Blog Docs

Missing client parameter


Please help I just started getting this error and noting changed in my side :frowning:

Search for clients or features
Notifications bell
Help & Support
Talk to Sales
SSO Integrations
Multifactor Auth
Hosted Pages
Anomaly Detection
Get Support
Occurred 3 minutes agoat 2018-03-16 09:52:59.086 UTC
Type Failed Login
Description missing client parameter
Context Data
“date”: “2018-03-16T09:52:59.086Z”,
“type”: “f”,
“description”: “missing client parameter”,
“connection_id”: “”,
“ip”: “”,
“user_agent”: “Mozilla/5.0 (Linux; Android 7.0; LG-H990 Build/NRD90M) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.109 Mobile Safari/537.36”,
“details”: {
“body”: {},
“qs”: {
“state”: “6KQivi0bZObQ1SAng2ZsIr4rwbdikbtL”
“error”: {
“message”: “missing client parameter”,
“oauthError”: “invalid_request”,
“type”: “request-error”
“hostname”: “”,
“log_id”: “90020180316095259086791065061152130280202273305692995634”
You have no new notifications.

Missing client parameter (again)

I’m receiving the same error. No code changes and just began getting this today.


We’re having the same issue. No code changes either.


Lately we have introduced a modification in the redirection between /authorize call and /login call that needs to keep the user session in order to work. For a normal end user that will work without any issue, however, we have seen tons of errors coming from User-Agents like Java and other tools that are not browsers. If you have an automated tool you will need to be sure that the tool keeps the session.


This was 100% happing from auth0.js running in Chrome browser. In any event this makes me nervous using this solution going forward, how can it work one day and the next throwing errors? This will loose sensitive customers for sure! There should be protocol’s ensuring this never never never happens with an authentication system…


Thank you for the verification - let me go back and see if I can track down what happened. Can you send me your tenant name so we can investigate? A DM is fine if you would prefer


It’s keeping several of our users from login in. We’re not using any automated tools, these are internal users/admins. Auth0 marked the incident as resolved yesterday but we’re still experiencing the issue. Tenant “pwnhealth”. Please advise.


Thanks for the info - I am checking internally and will get back with you as soon as I know something.


Hello Warren,

we are experiencing a simular problem when 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.

We will be creating a new ticket but wanted to let you know.



I’m having the same issue. Started this morning and preventing several clients from logging in.


So with this issue, quite often we see this happen when someone has bookmarked the login page and then try to hit that page - which will eventually not work after the session has expired - the login page is not meant to be bookmarked as it is shown as part of a non-repeatable OAuth 2.0 transaction.

Accessing /login will not work after April 1 as we deprecate old endpoints and instead push towards /authorize instead.


Is it possible to just route the user to the intended URL when this happens? We have some users that are not that technically savvy and are having issues like this. It would be easier if the login site just routed back to the original site instead.


Just to let you know. There are no bookmarks involved when looking at our problem.
The interface just keeps loading which in some cases result in a ‘missing client parameter’ error after a refresh.
And the problem only occurs on Android in combination with the Chrome browser.


Same here. No bookmarks involved. The error just happened to myself–I entered the URL of the application directly into the address bar and got the error screen with that message. Then I opened another tab and did the same again, it redirected correctly. Using Chrome on Mac.


To better provide an answer as to what is going on, and what changes should be made (@warren1 / @jnovak / @athome / @dennis1 / @jaliperti1 / @gmilow ), we need to know what/how you’re using Auth0, essentially the usecase. Feel free to DM me if you would prefer.

For instance, @athome where is that URL coming from? You can enter into /login with same values as before or be redirected by /authorize. Both, currently work. But if you’re making requests directly to /login that will need to change, otherwise some people may periodically see issues related to a lost session when the redirect comes to /authorize


Using Ruby on Rails SDK, implemented just like in the tutorial. Sample URLs: and . It was working until yesterday.

It’s working fine on 95%+ of the attempts, but there are some users that just can’t sign in. Keep getting the same error message. We’re seeing a lot of iPhones and Chromes on Mac in the user_agent of the error message. But doesn’t seem to be exclusive to that. We also can’t replicate it reliably, just happens randomly apparently.


In case it’s relevant, we’re using SSO. There are a few client apps that authenticate with that tenant. That’s also not new for us though.


Hi Jeremy, attached a screenshot of where we get stuck in the proces. It’s the out of the box 2FA authentication provided with Lock and Gardian. The screenshot is with Android and Chrome and with those we have the issues. Not always but nine out of ten. We happily provide you with more details if so required.


I used a tutorial I found on your site using auth0.js as is. Using it through a web. 100% No bookmarks. Also it was working perfectly for the last 2 month’s and started happening without making any changes.


Hi Jeremy, attached an image which contains some more technical information.