Caching in Actions

[avnish]

I have the same need. The use case is to call custom API from auth0 action.

[vigi]

Really disappointed that caching isn’t available in Actions like in Rules. Back to rules I suppose.

[nick.silvestri]

This seems like a fundamentally missing feature from actions. With token caching being recommended across Auth0 documentation, it seems like a complete oversight to not support it in the platform itself, especially when there’s a big warning on the top of the Rules page, which would be the cacheable alternative.

[dan.woda]

Hi all, I moved these requests to their own feedback item specific for a caching mechanism in Actions.

On this front, our team is actively investigating a solution for this. Stay tuned for more info.

[matheus.souza]

I have the same need!
Is there a way to cache on auth0 actions?

[dan.woda]

Hi folks, this feature is now live!

Read more here: Actions Caching Is Now Available

[dominik.wloadarz]

According to this article (Actions Limitations), the overall cache size is 8192 bytes. It means that not too many tokens can be stored there. Could you also provide a working sample of an Action that implements this feature?

[dan.woda]

@dominik.wloadarz, we are working on an example FAQ. We can post it here when it is published.

cc: @tyf

[tyf]

@dominik.wloadarz Here’s an FAQ with a rudimentary example:

Caching Management API Access Tokens in Login Action

Problem statement: How do I cache a Management API access token(s) using the Node Management Client and Actions caching functionality? Auth0 recently announced the ability to cache tokens within our extensibility solution, Actions. This has been a much requested feature that we are excited to have finally released. As many users utilize the Node Management Client to interact with the Management API by way of Actions, the question of how to incorporate the new caching functionality has arisen. S…

Note that you also have the ability to remove tokens from cache with api.cache.delete(key) - See documentation here:

Actions Triggers: post-login - API Object

[dominik.wloadarz]

According to the implementation it seems that one would be capable of storing maybe up to 8 tokens (assumption 1 jwt == 1kB) and that’s it (action limitations → 8kB of cache). So in a M2M scenario 1 API would be able to use up to 8 clients?

[ryan.fielding]

Agreed - this seems like a big limitation considering the use case it is supposed to be addressing.

[dan.woda]

@dominik.wloadarz @ryan.fielding,

Thanks for the feedback. Are you running into issues with the cache size limits in practice? The cache is ephemeral, so it may not be holding all those tokens at once.

Also, could you please expand on the following use case?

@dominik.wloadarz

So in a M2M scenario 1 API would be able to use up to 8 clients?

[jhu7]

According to the documentation action cache only persists 15 minutes. M2M tokens usually are valid for much longer (12-24 hours), let’s say I want to limit each client to 5 m2m token requests per day, action cache still can’t help me achieve that.

[dan.woda]

@jhu7

let’s say I want to limit each client to 5 m2m token requests per day, action cache still can’t help me achieve that.

Thanks for expanding.

This feature addresses token requests on every individual action execution and brings parity to the existing token cache feature in our legacy solution, Rules. You are correct, it will not provide a long-lived cache.

[jhu7]

Thanks for the response Dan. Are there any plans on the dev roadmap to provide built-in solutions for auth0 users to control m2m requests on finer scale (per application)? It always makes us nervous knowing someone may put on a loop and exhaust our quota for m2m token requests

[dan.woda]

@jhu7

There is a request for it here: Add rate limiting and cache for m2m token authentication endpoints

Feel free to add context to that thread.