Web Connector for Customer Web API
Is anyone familiar with the OAuth2 handshake between Power BI's "Web" connector and the AAD? I have a customer with a proprietary web api. The API can be changed as needed to perform the oauth2 handshake that generates an access token for use by the Power Query import. But no matter what we do, the handshake is not being performed correctly. The web api starts by properly generating the HTTP 401 WWW-AUTHENTICATE, and that gets us pretty far. But the error we are getting from Power Query is very problematic: "invalid_resource / resource principal was not found in the tenant". See image: For some reason the "Web" connector is not very flexible, and requires a strict resource URI. It always expects to use a rigid one that is based on the HTTP address: IE. see docs https://docs.microsoft.com/en-us/power-query/connectorauthentication "Power Query would expect your Application ID URL value to be equal to https://api.myservice.com." I guess in our example, the resource URI that it is probably requiring is http://localhost (not https://api.myservice.com). But we don't wan't to use a URI that is based on the HTTP address. If there are any Power BI experts who are familiar with the Oauth2 handshake which is used for the "Web" connector, I would greatly appreciate some feedback. Side note: The inflexibility of this Oauth2 handshake is pretty problematic by itself. To make matters even worse, the Microsoft AAD is now requiring resource URI's to be in a "verifiedCustomDomain". See https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-breaking-changes#appid-uri-in-single-tenant-applications-will-require-use-of-default-scheme-or-verified-domains This gives me little hope that a local IIS Express API would work (hosted on "http://localhost"). How can we connect the Power BI "Web" connector to a local web service that is actively under development? if anyone has AAD tips, they would be appreciated as well.
