Problems with OAuth2.0 and custom connector in Power BI Service

[Anonymous]

Hi

I have developed a custom connector that gets data from a REST API using the OAuth2.0 authentication scheme. It works perfectly in Power BI Desktop; once I type in a request, a login window pops up where I write the necessary credentials, then I am redirected to Power BI with the desired data. I have also published this report to Power BI Service, and I want to make a scheduled refresh of the datasets. To do this, I have installed a personal gateway. Under the dataset page I can click "edit credentials" ("rediger legitimasjon" down under), the usual login window pops up, I type the correct credentials, the login window dissapears and I get the following error message:

| Unable to refresh the model (id=8769990) because it references an unsupported data source.
-- | --
Cluster URI: | WABI-NORTH-EUROPE-redirect.analysis.windows.net
Activity ID: | 30259135-65cb-4381-8931-23cca2e8b02e
Request ID: | cebaf75b-8a7b-85a7-acfa-de69799b8204
Time: | 2019-12-16 13:21:06Z

Does anyone have a clue on how to resolve this issue? Any help is greatly appreciated!

Kind regards,

Angela Maiken Johnsen

[v-lid-msft]

Hi @Anonymous ,

How about the result after you follow the suggestions mentioned in my original post?Could you please provide more details about it If it doesn't meet your requirement?

Best regards,

[v-lid-msft]

Hi @Anonymous ,

Could you please check if your custom connector is within the Folder and enable the option in the Gateway?

If it is all configured, please check the query using Web.Content, if there are combined url in it such as following:

 Source = Json.Document(Web.Contents("https://api.powerbi.com/v1.0/myorg/groups/"& id &"/datasets", [Headers=[Authorization="Bearer " & TokenParameter]]))[value]

We can try to change it to using RelativePath to resolve some issue:

Source = Json.Document(Web.Contents("https://api.powerbi.com/v1.0/myorg/groups/",[RelativePath= id &"/datasets", Headers=[Authorization="Bearer " & TokenParameter]]))[value],

Best regards,

[Anonymous]

Hi @v-lid-msft, and thanks for the reply!

The custom connector is configured as in your screenshot, so that is not the problem here. 
As of today I don't have a combined url, but it may be the case that I have to do this in the future, so thanks for this tip. This shouldn't be required now as the user provides the whole url.
The Web.Contents part looks like this:

Source = Json.Document(Web.Contents(url, [Headers = [Authorization = "Bearer XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
Accept= "application/json", ...]]))

As you can see I haven't parametrised the token yet, but I am using a valid token as each token is valid for 150 days. So there has to be another problem, right?

Kind regards,

Maiken