We’re excited to announce that we’ve added the ability to cache tokens within our flagship extensibility solution, Actions. As part of our focus to continue positioning Actions as the core extensibility product within our platform, we’re adding new features to improve the efficiency of your developers. Actions caching is just one of the many ways we’re planning to improve the developer experience with Actions.
Caching within Actions
Available now, developers using Actions can leverage caching to reduce the overhead of obtaining tokens or re-fetching data in Actions. This means we’ve enabled machine-to-machine token caching so users no longer need to create new tokens but can instead cache existing tokens in a no-code environment. This feature is available in public and private cloud deployments.
Why Are We Releasing Caching within Actions?
Requesting and storing tokens over time for external services or machine-to-machine exchanges can drive up overhead costs and further exasperate latency issues. Caching can help mitigate these challenges while helping developers avoid exceeding their quotas on machine-to-machine exchanges and to improve performance and efficiency.
We’ve listened to these concerns and the needs of our developer community and vow to continue innovating Actions as developer needs grow. Actions caching, a means to minimize the number of machine-to-machine access tokens generated to authenticate with Auth0 APIs, is one way we’re accomplishing this. By allowing developers to cache tokens rather than create new tokens every time, we’re enabling you to reduce developer overhead while improving performance by eliminating the need to create new tokens.
The goal of allowing caching within Actions is to provide developers with a well-defined means to store artifacts such as:
- API tokens for third-party services to reduce latency between Auth0 and external applications
- Auth0 Management API tokens for improved performance
- Ephemeral data between Actions (or triggers), making data from one Action available to later Action(s) within the same flow
Next Steps
Ready to start taking advantage of caching within Actions? We have detailed guidance on Docs to help get you started. Please share any feedback or questions on your experience with Actions caching or Actions in general within our Developer Community.
Still Using Rules and Hooks?
As we shift our focus to make Actions our core and only extensible product within our platform, we highly encourage you to make your move from Rules and Hooks to Actions. Actions provide a developer experience that includes an industry-standard VS Code style editor, typescript, draft mode, version control, single-Action runtime upgrades, improved secret management, an expanded library of NPM modules, and much more. We’re continuing to release exciting new features within Actions that will not be available for those still using Rules and Hooks. In order to take advantage of the reduced developer overhead and improved performance of caching, you need to be using Actions.
Don’t know where to start? Visit our Move to Actions page for demos, feature comparisons, and docs for migrating from both Rules to Actions and Hooks to Actions.