Issue with OIDC Configuration Validation During GitHub Actions Deployment

Help
,
1

Hello Auth0 Community,

I’m currently facing an issue while deploying our Auth0 tenant configuration through GitHub Actions, and I’m hoping for some insights or advice.

We are migrating our Auth0 setup to our codebase using GitHub Actions. To do this, we exported the existing tenant configuration with a0deploy export --format=yaml, which produces a tenant.yaml file along with other resource configuration files. The goal is to update parts of the Auth0 configuration and then deploy the entire setup using a0deploy import --input_file ./dev/tenant.yaml.

The Issue:

Upon attempting to deploy the configuration, we encounter the following error:

Bad Request: "options.oidc_metadata.scopes_supported" must contain less than or equal to 200 items

This error suggests that our OpenID Connect (OIDC) configuration has more than 200 scopes listed in the scopes_supported field. However, this is the same configuration currently accepted and operational in our Auth0 environment, which makes this validation error puzzling.

Questions:

  1. Has anyone else experienced a similar issue when exporting and importing tenant configurations using Auth0’s CLI tools?
  2. Is there a known limitation or bug related to the number of scopes in the OIDC configuration when deploying via GitHub Actions?
  3. Any suggestions on how to troubleshoot or resolve this issue would be greatly appreciated.

Thanks in advance for any help or insights!

Best,
David

4

Hi @davidatsafety,

Welcome to the Auth0 Community!

You mentioned that you updated parts of the exported tenant.yaml file configuration before deploying the setup onto your new tenant.

Could you clarify if you were able to import the tenant.yaml file without making any changes from the export?

As for the error you experienced, it indicates that the scopes_supported has over 200 items and is not allowed. Could you check if your existing tenant has over 200 items in its scopes_supported?

Thanks,
Rueben