Hello,
We’re trying to enable a custom url for our tennant, I did all the configuration required and everything seems set up right. When I go to the url I can see the following error.
There was an error fetching the SSO data. This could simply mean that there was a problem with the network. But, if a "Origin" error has been logged before this warning, please add "https://my.url.com" to the "Allowed Web Origins" list in the Auth0 dashboard: https://manage.auth0.com/#/clients/{myClientId}/settings
Adding the url to the “Allowed Web Origins” didn’t help. When I watch my network traffic I can see that the default url (https://my-tennant.eu.auth0.com/user/ssodata) is called but on my custom domain it isn’t.
We use the default Lock object with a customized login page with version 11.4.0 and the client I am testing this with is OIDC conformant.
Strange thing is that we have multiple tennants and on our dev tennant (our oldest tennant) with the same configuration it works and calls the endpoints that I expect. When I look at the configuration object that Auth0 fills in I can see one difference which seems strange but I don’t know what the reason is for it.
When I visit the custom url on DEV it switches, if I go to the tennant authorize endpoint it will get filled with the url that I’m visiting, but on our UAT tennant it seems static and is always being filled with the tennant endpoint.
- “auth0Domain”: “my.url.com” (DEV environment, is getting filled with the endpoint I’m visiting)
- “auth0Domain”: “my-tennant.eu.auth0.com” (UAT, always pointing to Auth0 tennant domain)
Anybody else having this issue or that knows what’s going on here?