Forum Discussion
Helper VCustom Connector, Gateway & OAuth
Super UserAs the error message says - if you provide your own callback URI then you need to make sure whatever is at that URI will respond correctly to the callback.
Helper VThe callback URI should be supplied via the OAuth workflow, I don't supply it, the return of the value is baked into Power BI's handling of OAuth.
I modfied my error message to include the full URI callback string and in reviewing the results its not actually the callback URI, it is the initiation URI that is passed as part of starting the process. Basically it is attempting to iniaiate the process, but then fails and goes straight to the Finish step (so not really a very elegant failure mode). This would align with the fact that a browser window appears briefly where I should be able to grant access as part of the OAuth workflow, but that window quickly disappears.
For anyone curious the URI contains the key for code, but there is no value, response_type is also blank.
Thus the question is, does anyone have tips on how to deal with the fact that there seems to be some issue with iniatiting the OAuth workflow, or is this simply one of the litany of issues with the OAuth workflow?