Automation Cloud Authorization URL not working

Help Orchestrator
,
1

Hey folks,

I am stuggeling with the setup of an API connection to my Community Cloud Orchestrator using OAuth2.0

I have registered a confidential external application and added a couple of User scopes that I will need later on. I retrieved Application ID and Secret from the Popup that appears after the registration.

I then to tried to establish the connection from my external app (Power Automate in case it matters) by following the documentation here:
https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/setting-up-the-external-application#using-the-different-grant-types-authorization-code

According to the documentation, I am supposed to use the authorization URL “UiPath” to authorize my requests. However I have tried multiple different ways (PowerAutomate, Postman, entering URL directly) and I am always getting the following result:

image
image853×339 8.17 KB

Happy to provide yu with further information if needed. Hope anyone can tell me what I am doing wrong.

2

Check this article https://uipath-survey.secure.force.com/CaseView/articles/Knowledge/How-to-use-UiPath-External-Application-with-User-Scopes-in-Power-Automate?lang=en_US

3

Hey Marian,

thank you for sharing the article. I have not seen that one. I followed the same steps, but my I get stuck on step 6a) of this set of instructions. After clicking on ‘New connection’ in PA, a screen appears with the message as screenshotted in the original post.
I noticed that the URL there is not the same as the Authorization URL that I was giving it in PA:

image
image1289×881 23.5 KB

Any further ideas what I could be doing wrong?

4

Double-check the article as it seems something you missed.

5

@Felix_Rech1

Please check this

cheers

6

I found my mistake - My redirect URL in the application that I set up on the Automation Cloud looked like this:
image
After removing the trailing slash, th authentication is now working. Thank you for sharing the documentation. Much appreciated. I followed it closely a second time and therby found my issue.

In addition, I have the feeling that switching to a different browser also helped. Maybe I had some cookies saved that lead to wrong credentials being used for authentication.