I have a site setup and working perfectly - in the development environment using localhost:4205 and for the callback api localhost:5005
Now, I’m trying to set the URL to https://Real-Site.company.com . and I’ve added that as a valid Callback, and CORS (says it isn’t needed). And both the API and the main pages will be sent to this same server.
When I redirect to the mayaccount.auth0.com/authorize and specify a clientId (same as before), scope (same as before), audience (new URL instead of localhost…), nonce (same as before), and response_type=id_token (same as before)…
It comes back with an error of ‘service not found: https://Real-Site.Company.com’ - looking in the logs gives much greater detail! It says "service not found: https://Real-Site.Company.com’ . Thanks for the great log message, and the information on how to fix the problem right there in the logs so I don’t have to post this message and wait… (Oh, well, nevermind…)
So, Um, where is it looking for this service that it can’t find? I tried creating an API (like I had to do for the other one because the other one had a different site name for the API) and that didn’t work. I tried creating it with and without the trailing /
I’m ready to roll this out to 3 sites (common login in all 3 + development), and I’m blocked by it being weird.