Skip to Content
Dec 06, 2021 at 11:35 AM

Approuter in a service to approuter scenario doesn't work in a client_credentials oauth case. Why?

195 Views Last edit Dec 06, 2021 at 11:42 AM 2 rev

Dear community,

I'm trying to use the approuter to access a destination defined at instance/subaccount level (/ because I tried both without success) in a service to approuter scenario. I'm using this approach with the x-approuter-authorization header:

The thing is that it works if I use an authorization code oauth2 flow, it doesn't in case of client_credentials.

In case of client_credentials the flow works well in case of destination defined at environment level, not in case of service instance/subaccount. In this case it returns "500 Internal Server Error".

In the log I can see this: GET request to "service_accessible_via_destination" completed with status 500 401 - {\"error\":\"unauthorized\",\"error_description\":\"Unable to map issuer, https://"my_subdomain" , to a single registered provider\"}

Do you know why?

Many thanks in advance,

PS: Working just with the destination defined at environment level is not an option because of auth things