Access Token returning "Unauthorized request"

Recently, our refresh_token started producing access_tokens that return "message": "Unauthorized request" for any graphql call made. I just tested creating a new access token through the CURL command in the docs to verify. These are inherently different than the token expired messages we are used to where we check for that case explicitly: if (message === "Bad token" || message === "Token is expired") {...,

We also have a developer account that we utilize for staging whose access tokens currently work. As a temporary solution, I have changed our production instance to point to this developer account.

I’ve also double-checked the scopes of both of the access tokens, and they are the same.

If this is any help, according to our error handling, we had this happen one-off on August 3rd, August 15th, and October 8th. Since those errors are coming from a specific cron job that is run every ten minutes, I can confidently say the issue resolved itself quickly each of those days. However, it has permanently been erroring for us since October 24th.

Appreciate the help. Did not want to post any sensitive account tokens, so just let me know what you need from me to further debug. Thanks!

1 Like

Hi @kevin
Thanks for reaching out!

Is this for the same email you are using on this post?
Thanks in advance!

Hey @tomasw! Yup, my email is linked to the developer account

Thanks, @kevin!
Allow me to do some research on your user and see if I can find anything.
I will let you know asap

Thanks again for the patience!

Hi again @kevin!

We don’t have logs for that user at the moment, it is an active user, but recently we made some adjustments to our Auth0 integrations and that information might be lost.

We just reset your user on our platform.

Try the following:

  1. Generate a new Bearer
  2. Use the refresh token got in step 1 to re-generate a new Bearer

And see if it works as expected now.

Let me know if with that new refresh token you keep having issues.

Thanks again!

Hey @tomasw, followed those instructions and everything is in working order again. Appreciate the help!

1 Like