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.
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…
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.
1 Like