Hitting 30 Secrets per Action Limit

Knowledge Articles
1

Overview

This article explains how to avoid hitting the 30 secrets per Action limit.

Applies To

  • Actions
  • Secrets Limits

Solution

First, ensure that the variables stored in the secrets are real secrets. If the information stored in the secret section is sensitive, like a token or client secret, the following two options may be helpful:

  1. Using one secret for multiple attributes: The value section of a secret can hold up to 4096 characters and be used simultaneously for multiple secrets.

  2. Splitting the logic into new Actions: When the 30 secrets per Action entity limit has been reached, it may be possible to use a new Action and segregate the logic to add more secrets in the following Action.

If the variable is not a real secret, the following solutions may used instead:

  1. Using metadata for storing the custom information: Organizations and applications have metadata sections that keep organization and application variables. These can be accessed from Actions and can be used. If the variable is user-level, storing it in the app_metadata section of the user profile may be possible.
  2. Inserting the variables in the Action code: Nonsentive variables can be managed directly in the Action code itself. Action updates using the Auth0 deploy CLI tool or Auth0 Terraform provider can help automate change management.