APIM Custom Connector - 401 Unauthorized Response - Access denied due to missing subscription key (Ocp-Apim-Subscription-Key)

(1) Share

Report

Posted on by banukasonel

Created a custom connector using Azure API management. Initially this was working. I made some changes in one request and updated the connector. After updating I am receiving the 401 Unauthorized Response - Access denied due to missing subscription key (Ocp-Apim-Subscription-Key)

This works if I remove subscription required tick in Azure API management. But I don't want to allow access to this API without subscription key.

Below is the response header

{
 "x-ms-apihub-cached-response": "true",
 "x-ms-apihub-obo": "false",
 "WWW-Authenticate": "AzureApiManagementKey realm=\"{API_BASE_URL}/tm-power-clone\",name=\"Ocp-Apim-Subscription-Key\",type=\"header\"",
 "Date": "Tue, 02 Jan 2024 04:03:30 GMT",
 "Content-Length": "152",
 "Content-Type": "application/json"
}

Categories:

Connector development

I have the same question (0)

All responses (1)

Answers (0)

mannybellas1 3 on at

Like (0)

Report
Copy link

Link copied!
I have similar issues, too. It happens when I update the Custom Connector through any of the following mechanisms
from APIM
or if I update it using `pac connector update`
Import it from a managed solution
Annoyingly, I found I could fix the issue by opening the Custom Connector in the environment, clicking "edit" and then "save" without changing anything.

I think I saw somewhere mentioned that updates to the connector might take a moment to apply, but I haven't tested this.

Was this reply helpful? Yes No