Issue with creating custom connector for UiPath in Microsoft Power Platform using oAuth 2.0

[Mayeusz]

Hi,

I have some issues with creating a custom connector in power platform for our Orchestrator platform, using oAuth2.0.
Our set up is on-prem installation, and I have already registered an application in Orchestrator.
When it comes to the authorization mechanism, we set up confidential application type, user scope, where the required grant type is authorization code.

Whole set up has been performed based on the UiPath article: Orchestrator - Accessing UiPath Resources Using External Applications

I’m also attaching, how everything is configured in power platform.

Basically when Im trying to establish new connection for custom connector, no error appears. Im able to see Orchestrator pop up, where I have to authorize myself. After a while, another pop up appears for a second saying: “Authorization completed” - but after that, no new connection appears on the list, it is still blank, and I cant see any error, so something is still wrong.

I have tried exactly same things in postman, and everything works fine, no issues, so its only related to power platform.

Any ideas what might be wrong?
Maybe some changes in the web.config file are required?

[trotter (Kiel Trotter)]

Hello,

I am currently working through the same issues. I am able to get past this portion by checking the connect via on-premises data gateway. This has a different problem because Azure doesn’t allow oAuth2.0, but I can at least make use Authorization end point. I just don’t know how to actually authorize other calls after that. The check box I used was on the General information section.

[Mayeusz]

Yes, same problem on my side - just authorization part works, and it also works fine using gateway, but the thing is to switch to oAuth2.0 which doesn’t work at the moment.