Authentication Issue: No Refresh Token Found in Cache

Question

Hello Support Team,

I am encountering a persistent authentication issue while attempting to access Azure services through our application. Below is the error message received during the authentication process:

Errors: [
  {
    "errorMessage": "no_tokens_found: No refresh token found in the cache. Please sign-in.",
    "clientId": "c44b4083-3bb0-49c1-b47d-974e53cbdf3c",
    "scopes": [
      "https://management.core.windows.net//.default"
    ]
  },
  {
    "errorMessage": "no_tokens_found: No refresh token found in the cache. Please sign-in.",
    "clientId": "c44b4083-3bb0-49c1-b47d-974e53cbdf3c",
    "scopes": [
      "c44b4083-3bb0-49c1-b47d-974e53cbdf3c/.default"
    ]
  }
]

The application is failing to retrieve a refresh token from the cache, which is preventing access to Azure services. This issue persists even after attempting to sign in again.

Could you please assist in resolving this issue as it is impacting our ability to operate effectively on Azure? Any insights or corrective actions that can be recommended would be highly appreciated.

Thank you for your assistance.

Answer 1

Hello @Mohamed CHIHA

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue:

Authentication Issue: No Refresh Token Found in Cache

Solution:

you have resolved the issue by synchronizing the time zone with the internet.

If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

Answer 2

Hi @Akhilesh @Hadi Bin Noor ,

I resolved the issue by synchronizing my time zone with the internet.