I have developed a custom connector that uses OAuth2 "authorization_code" flow. Everything works fine in Power BI Desktop and I can get authorized and load data.
I then installed the On-premise data gateway (personal mode) and enabled custom connectors. My connector shows up and after publishing a report that uses this connector I was able to edit the data source credentials and signin via the connector. The sign in completed successfully and everything appears to be okay.
I then click refresh now and it attempts to refresh the data set, but after only 10-20 seconds it has failed with the following (It wouldn't let me insert an image to I copied the relevant information):
There was an error in the data gateway.
Underlying error message: Object reference not set to an instance of an object. Table: Selected Properties. DM_ErrorDetailNameCode_UnderlyingHResult: -2147467261
Selected Properties is one of my queries, but which query it fails on varies between refresh attempts so I assume it is failing on whichever query executes/completes first.
Any help as to what this could be would be greatly appreciated!
I'm dealing with the same issues. Here it says: "OAuth isn't a supported authentication scheme with the on-premises data gateway. You can't add data sources that require OAuth. If your dataset has a data source that requires OAuth, you can't use the gateway for scheduled refresh."
No luck, I tried again today and now after clicking "Edit Credentials" on the customer custom the window opens and I can sign in. But after the redirect the window closes and just sits in the edit credentials window.
Closing that window and clicking edit credentials again breifly pops open our sign in page which immediately closes, which I assume means that I already have a valid token and am being redirected.
I managed to make it work, it was a problem in one of my functions (I will check if I remember which one) And I can confirm that Custom Connectors do refresh through the Gateway (no need to be the personal one).
EDIT: Found it. I implemented a logic developed by Matt Mason in the TokenMethod function. After this change, it worked.
@CAOP Thanks for the reponse, the issue I'm experiencing is actually after I get authenticated and attempt to refresh the data set.
You did help me identify a bug in my token refresh, so thank you very much. I was doing something very similar in regards to switching the parameter name depending on whether it was an access token request or token refresh. Turns out the documentation was lacking and I had the wrong name for the refresh token tokenField parameter.