Share
Report
79Hi!
I have set up a custom connector, nothing fancy or custom code, just plain old custom connector. The API I´m trying to call use OAuth2 for authentication. The auth part seems to work, I can establish a connection without any problems.
However when I try calling the API i get a 403 response and no information about why. So something is obviously not working.
Here is the part where I get more confused, the call that respond with 403 seems to be an "internal" call to azure, the request looks like this: https://europe-002.azure-apim.net/apim/{myConnectorName:{LongGuid}}{endpoint_for_api_Im_calling}.
As I understands it (guessing), the custom connector itself doesn't make the API call to to endpoint we specified. The connector calls "something on Azure" that makes the actual API call and then returns the respond to the connector.
So is it Azure returning 403 or is it my Saas API that I'm trying to call that returns 403? Anyone that could enlighten me and point me in a direction how to solve this? Is there a way to se the actual request call somewhere and not the Azure call?
I have multiple custom connectors with OAuth that works just fine and I cant see why this one is any different.
All responses (
Answers (
