Geting invalid client identificator | Community
Skip to main content

Geting invalid client identificator

  • July 14, 2022
  • 2 replies
  • 0 views
Marta13

On the second step of authentication - exchanging the code for a token, while building our app we get: 

{"error":"invalid_client","error_description":"The client identifier provided is invalid, the client failed to authenticate, the client did not include its credentials, provided multiple client credentials, or used unsupported credentials type."}

We are testing with our own account that has created the local app, the client_id is valid when passing it to https://[subdomain].zendesk.com/oauth/authorizations/new, however on https://[subdomain].zendesk.com/oauth/tokens we get this error. 

Is there an issue with testing the application development, we are on a sponsored account: d3v-oveosupport

 

Thanks for your help, 

Marta

 

    2 replies

    Tamara12
    • Tamara12
    • July 14, 2022

    I get different error on the same request Marta mentioned (with exactly the same Body-parameter):

    {
        "error": "invalid_grant",
        "error_description": "The provided access grant is invalid, expired, or revoked (e.g. invalid assertion, expired authorization token, bad end-user password credentials, or mismatching authorization code and redirection URI)."
    }
    Eric27
    • Eric27
    • July 14, 2022
    Hey there,

    You mention that you're testing these from local. Are you saving these as secure parameters in your manifest file? If so that'd be why you're running into this issue as secure params are not able to be loaded from local builds. If not, please provide the code snippets of how you're making these calls and we'll take a look.

    Thanks!

     
    Terms & ConditionsCookie settingsAccessibility statement