Access token invalid for client

  • Our SSO flow was working since I deployed the feature at the start of September. Then, our client noticed it not working yesterday. We’re getting a 400 error when making the /oauth/token request:
    '{"error":"invalid_grant","error_description":"Authorization code doesn\'t exist or is invalid for the client"}'

    I tried Justin Greer’s (plugin author) suggestion from another thread to deactivate and reactivate the plugin to rule out any time sync issue (also tried w/ a complete reinstallation). However, that didn’t fix the issue. I have the latest version of the plugin as well.

    What else could be the issue? Not sure if it’s related, but the SSL certificate verification failure was the 1st issue we noticed and are using the verify=False option for now.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter sliao

    (@sliao)

    I figured out my issue in my production environment, which wasn’t related to this error. However, I’m still curious about this error, which I saw in my development environment. Does this error get returned if we started our request (getting a code to append to some url [domain A]) w/ domain A and continued the flow/testing with domain B? Is that a built-in security feature that disallows that?

    Plugin Author Justin Greer

    (@justingreerbbi)

    Hi,

    This may be a server time issue in your development environment. If it is working n production and not development, this may be the case. We often see things like this for when servers are updated, moved, etc and the time is knocked off.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Access token invalid for client’ is closed to new replies.