Custom Connector - On-premise Web API not working

[BarryBarkley]

Hi,

About 4 weeks ago, I created a simplistic on-premise ASP.NET Web API 2.0 solution and I could successfully use it in a Flow via the On-premises data gateway.

But now, I get the following error when testing the connection:

{
"status": 401,
"message": "No matching shared key found",
"source": "gatewayconnector-we.azconn-we.p.azurewebsites.net"
}

I followed the steps here: https://flow.microsoft.com/en-us/blog/on-premise-apis/

but I can't figure out where the issue is now.

I'm not using Authentication to keep things simple for the test.

Since I'm following the same steps as 4 weeks ago, I'm assuming something has changed on the Flow side and a bug might have been introduced.

Any help would be greatly appreciated.

Cheers

[v-yamao-msft]

Hi @BarryBarkley ,

Could you try to recreate the connector to see if it will work?

If the issue still exists, please feel free post back.

Best regards,

Mabel

[JoeO]

Im having the same issue on a custom connector which i recreated multiple times. It returns "No matching shared key found (401)". I opened a case and waiting for a reponse. Case# 119022221000897 

[NikitaUs]

It seems somthing wrong with custom connectors engine since I am fasing exact;y the same issue. At the same time I am able to get data via on-premise gateway inside "Data integration projects".

I've created issue in PowerApp support (119030222000246) several days ago but didn't get any response.

[NikitaUs]

Did you found solution? I had a call with support and their answer was it is something wrong with your service. It was actually pretty strange since I can consume data in integration project for the same gateway.

[NikitaUs]

@BarryBarkley Did you found solution? I had a call with support and their answer was it is something wrong with your service. It was pretty strange since I can consume data in integration project for the same gateway. So they offered me to find someone who know how it works

[LeszekF]

Hi @NikitaUs 

Did you find solution for this issue?

I set up On-permises Data Gateway 5 days ago. It used to work back then. Since yesterday I am having the same issue. I've tried couple of things, but so far no success.

[BarryBarkley]

Hi,

Unfortunately, I haven't found a solution yet.

Luckily my issue isn't critical yet as I was merely testing the process to do a demo to colleagues.

The custom connector I built before the issue started, still works in production, but I can't build new ones.

Kind regards,

Barry