Are Auth0 Client Credentials being cached?

💬 Queries and Resources
1

As the title suggests, we'd like to know how and why this is happening. Steps to reproduce:

  1. Use an app that has a resource that uses Auth0 Client Credentials
  2. Change the Auth0 Client Credentials and save
  3. Old credentials are still used for up to a day

Expected:

Old credentials are no longer used.

We've come across this issue a few months ago whilst setting up Auth0 Client Credentials and submitted a support email but it magically started working the next day. We've also come across it more recently due to an Auth0 Tenant migration which is quite annoying as it means the migration takes at least a day.
It appears others are also having this issue as well: Auth0 Token Auth Returning "undefined" Token

To us it seems like there's some definite caching going on with the client credentials, secret and audience. Other changes to the resource settings are immediate such as the API URL. We inspected via logging and confirmed Retool is sending old credentials.

We'd like to know:

  1. Why are these fields being cached? Seems like a bit of an issue especially if you are in our situation whereby a whole environment is unusable because it's using old credentials.
  2. How long is the cache TTL?
  3. If the cache is necessary, can you at least clear it once changes are made to the settings?

Thanks in advance!

1 Like
3

Hi @marcus_sohonet,

Thank you for bringing this to our attention. I just pinged out engineering team to get some answers to your questions.

Once i hear back from them I can either confirm that caching is necessary or if this is a bug. If caching is necessary I can look to have the engineers expose an option to invalidate old caches on saves as that is what I would expect and is that definitely should be happening regardless.

Apologies for the inconvenience and will report back once I hear from engineering!

4

Hello Jack_T,

Any update on this, I have the same issue on my self-hosted instance.

Best,
Erwan Bernard

7

Hi @Erwan_Bernard,

I just raised this issue with our engineering team. They are looking to reproduce this Auth0 behavior so as to figure out what could be causing the improper caching and fix that.

I will update you with any news I hear from them, if you can share steps to reproduce the behavior you are seeing that would be very helpful and I can share that with our engineers :+1:

11

Hi folks!

Great news, it appears that the ticket for this issue has been marked as done by our engineering team and there should be no more unintended caching.

The change will likely be going live shortly in our next release to cloud customers.