UiPath Orchestrator APIs not working since Cloud Platform Release

Help
87

If you have an account created before last week you have to use the credentials that you used before the update. Link is different, now is UiPath
in kamal environment use the name of your service in orchestrator.

2 Likes
88

We have our own orchestrator with entreprise license but when i use this url xxxxxx.comĀ -Ā xxx sex videos free hd porn Resources and Information. i have a 404 error .

if i understand , we have to use https://xxxx.com/nameofourservice/nameofourservice/api/Account/Authenticate ? ,

2 Likes
89

@lndiop

Can you access the API definitions by navigating to an URL that looks like this:
http://platform.uipath.com/swagger/ui/index
but with platform.uipath.com replaced by your Orchestrator URL?

Leaving you with:
http://your.Orchestrator.Instance/swagger/ui/index

4 Likes
90

What can I do to make the Node-Red integration work again? What information should I put in these fields?

image

2 Likes
91

@marcelojrfarias - you should use the exact same username and password you used two weeks ago before the migration to cloud started.

3 Likes
92

Hello @loginerror ,
Yes i can access via SWAGGER but when i call Api directly in my html page. Iā€™ve a 404 error.

2 Likes
93

Ok so what credentials should I use if I made my UiPath account yesterday using the option to authenticate with my Google account?

2 Likes
94

Is this thread dead? Iā€™m having trouble authenticating using a newly created UiPath account linked to my Google one.

2 Likes
95

Hi @Jonny_Rogers. For new accounts you should follow the instructions under ā€œFor New Accountsā€ in this post: Consuming APIs with the new Cloud Orchestrator

Specifically, this is the document for you: About OData and References

Thanks!

3 Likes
96

Hi @tarekmadkour, thanks for your reply. Iā€™m not entirely sure how relevant the webhooks documentation is, but perhaps Iā€™m misunderstanding it?

Iā€™ve also had a look through the documentation on consuming the cloud API and gone through it manually. The access token that I received still didnā€™t work, I get ā€˜401 Unauthorizedā€™ when trying to use the postman collection found here.

The authentication process seems extremely convoluted, running nodejs to encrypt then copying sections of a URL is awkward to do manually and even worse when trying to do as part of an integration.

3 Likes
97

Hi @Jonny_Rogers

I believe this is the link indeed :slight_smile:
https://orchestrator.uipath.com/v2019/reference#consuming-cloud-api

Itā€™s a full guide on how to be able to authenticate your API requests with the new platform in cloud.

It tells you here how to make the calls:
https://orchestrator.uipath.com/v2019/reference#section-making-orchestrator-api-calls

Could you specify which call were you making that failed with 401?

3 Likes
98

The system stopped working as soon as you updated the authentication. In an attempt to make it work again, I reset the password as you reported being a possible solution to access the portal. Now Iā€™ve tried to authenticate with the old password and the new password, but none of them works. What can I do?

How do I use Node-Red to integrate with new accounts in the Orchestrator now in the Cloud?

2 Likes
99

HI @marcelojrfarias,

How did you reset the password? Did you reset it from the Portal WebPage?

Thanks,
Vijay

4 Likes
100

Hi, Vijay!

Yes! I reset my password through the web portal option ā€œForgot password?ā€. But it did not work and I still can not create new jobs through the node-red.

Thank you for your support.

2 Likes
101

HI Marcelo,

Iā€™m sorry that you are facing this issue. I just tried the forgot password thrice and tried updating the new password from the password reset email and it seems to be working for me. Hence asking the follow up questions.

  • Were you able to get the reset password email to your email address, when you enter your email address in Forgot Password?
  • Were you able to reset password from the link in your email and update the password?
  • If you were able to update the password, you were not able to login using this updated password?
  • Could you retry these steps again and see if you were able to reset the password now?

Thanks, and sorry for asking you to do these steps again.

4 Likes
102

Hi all,

Thereā€™s a practical example using the new authentication method at Robotic Process Automation and Low-Code: A Practical Tutorial on Integrating UiPath with Joget | HackerNoon in case you still have trouble authenticating.

Hope this helps!

5 Likes
103

Hello, @Vijay_Rajasekharuni!

I have been able to reset my password a few times without any problems. And the modifications take effect when I try to access the web portal, I always need to use the new password.

But even updating the password on Node-Red, I can not successfully create my jobs.

Iā€™ve tried some settings, but to no avail.

First attempt:
image

Second attempt:
image

Third attempt:
image

2 Likes
104

Hi Marcelo,

You are trying to use the Basic Authentication here when you are trying the username and password. This method doesnā€™t work in the Cloud Orchestrator. Please take a look at the steps provided in About OData and References to generate the refresh_token and access_token. You can create a HTTP request by adding Authentication and TenantName headers as mentioned in the document to make calls to Cloud Orchestrator.

4 Likes
105

Hi Marcelo,

This current method of authentication will work until July 15 on Cloud Orchestrator, after which only OAuth 2.0 will be supported. To make it work for now, change your URL to https://platform.uipath.com//.

Iā€™ll be updating the Node-RED connector to support the new authentication this weekend and will respond back here once itā€™s done.

5 Likes
106

Thanks for your help!

I changed the url to <https://platform.uipath.com/ 2 /> as requested (I tried https://platform.uipath.com/2/ too), but it did not work. Now I get a message ā€œCould not find a process named [my_process_name] in [my_environment]ā€

Iā€™m waiting for your update.

2 Likes