Yes. I tried filling out this OAuth UI, that’s when it’s telling me that the root domains do not match:
I even tried generating an access token manually and filling that out by setting “Authentication” to “API Key” and selecting “Bearer”. That just gave me “Error saving draft” without any details.
I mean, the error states something correct, the Auth/Token URL is indeed a different root domain than the API hostname. But I cannot fathom that being a limitation? Aren’t many APIs secured by a third party authentication provider - making these root domains different by default?
The “Client Id” and “Client Secret” values you fill in there when “Authentication” is set to “OAuth”; that’s for running authentication with the Client Credentials Flow, right?
That’s how I have tried setting it up so far at least, and I have verified that the same Client Credential token request returns a valid token from Postman.
Also, you openapi spec that you got working when also configuring this Authentication: OAuth; is that the one you linked initially as “openapi.json” (I’m not allowed to insert links in comments yet apparently)?
And then you configured the authorize/token urls to something like “…ttp://adzviser.com/…/oauth/v2.0/token” and “…/authorize”?