Can't set the default audience for a tenant

[ryan-cahill]

It is explained that the default audience in tenant settings should be an API identifier. An API identifier can be a string like “my-cool-api” but the default audience only accepts a string in the format of a uri. So if I wanted the default audience to be “my-cool-api” I would see the error ““Default Audience” must be a valid uri”.

I am confused by this inconsistency. Could someone shed some light on this?

[ty.frith]

Hi there @ryan-cahill welcome to the community!

I am seeing the same behavior you are - It looks like it’s only validated on the client side so using the management API to set a non-uri default_audience will work.

curl -H "Authorization: Bearer <token>" -X PATCH  -H "Content-Type: application/json" -d '{"default_audience":"<the audience>"}' https://YOUR_DOMAIN.auth0.com/api/v2/tenants/settings
 

Hope this helps!

[ryan-cahill]

Hey @ty.frith thanks for the suggestion. Instead, I already found similar issues that have been open since 2020 and created a new API with a random URL.

Bug? Cannot Set Tenant Default Audience (any more)

I have an existing Auth0 integration which has been working fine. It has an API with an identifier like my-api (notice, it is not a uri). The Tenant Default Audience is my-api. This has been working for well over a year. Today we tried to setup a new tenant. We created an api with the identifier my-other-api. I then tried to set the Tenant Default Audience to my-other-api. It threw an error saying the default audience must be a valid uri. Odd. So I tried setting the default audience to the ur…

Format for "default audience" must be URI. But API Identified can be standard string

It is explained that the default audience in tenant settings should be an API identifier. An API identifier can be a string like “my-cool-api” but the default audience only accepts a string in the format of a uri. So if I wanted the default audience to be “my-cool-api” I would see the error ““Default Audience” must be a valid uri”. I am confused by this inconsistency. Could someone shed some light on this?

Can your team please fix this issue? I don’t need help with this anymore, but this is an incredibly confusing UX.

[ty.frith]

Thanks for the follow up! It looks like this is in the backlog to be addressed - Sorry for the confusion!