I’ve been working on setting up an automated backup system for our Auth0 configurations, syncing them to GitHub using the Auth0 Deploy CLI (a0deploy). Everything was functioning smoothly up until this morning, when I encountered a new error during the export process.
** Here’s the error message I received:
2024-09-24T09:55:50.588Z - error: Problem running command export
2024-09-24T09:55:50.588Z - error: Problem loading tenant data from Auth0 Forbidden: Th
Has anyone else encountered this error when exporting Auth0 configurations using auth0-deploy-cli? Is it a rate limit issue because we are on a free plan? Due to the structure of our business, it will be challenging for me to provide Auth0 with additional card details.
Any insights or suggestions to help troubleshoot and resolve this issue would be greatly appreciated!
I have an update! It looks like the solution is to include your credit card information in your dashboard settings. This information is only used for verification, and you will not be charged for it.
I have included my credit card information in my dashboard settings. I am still unable to export, however the export error is different now. Here is snippet of the export log file:
a0deploy export --format yaml --output_folder=dev --config_file ./config/dev.json
2024-10-17T17:22:42.474Z - info: Loading Auth0 Tenant Data
2024-10-17T17:22:42.714Z - info: Retrieving rules data from Auth0
2024-10-17T17:22:42.854Z - info: Retrieving rulesConfigs data from Auth0
…
2024-10-17T17:23:10.851Z - info: Retrieving roles data from Auth0
2024-10-17T17:23:11.291Z - error: Problem running command export
2024-10-17T17:23:11.291Z - error: Problem loading tenant data from Auth0 Payment Required: A paid subscription is required for this feature.
The new error is: A paid subscription is required for this feature.
The error logs suggest that the issue is occurring when exporting your role information. The error states that you have Role-Based Access Control configured, but using this feature requires a paid subscription.
Thanks for the update. I disabled RBAC on my API that was using it, but that did not fix the problem. The same error persists.
This is all strange, because before the pricing update in early October, these dev exports were allowed regardless of RBAC usage or plan.
If this helps, these errors are occurring in my Development tenant which is weird because I would expect work in a Development tenant would not be restricted by Free versus Paid plans.