What can I do to make the Node-Red integration work again? What information should I put in these fields?
UiPath Orchestrator APIs not working since Cloud Platform Release
1 Like
@marcelojrfarias - you should use the exact same username and password you used two weeks ago before the migration to cloud started.
2 Likes
Hello @loginerror ,
Yes i can access via SWAGGER but when i call Api directly in my html page. I’ve a 404 error.
1 Like
Ok so what credentials should I use if I made my UiPath account yesterday using the option to authenticate with my Google account?
1 Like
Is this thread dead? I’m having trouble authenticating using a newly created UiPath account linked to my Google one.
1 Like
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: https://orchestrator.uipath.com/v2019/reference#consuming-cloud-api
Thanks!
2 Likes
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.
2 Likes
I believe this is the link indeed 
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?
2 Likes
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?
1 Like
HI @marcelojrfarias,
How did you reset the password? Did you reset it from the Portal WebPage?
Thanks,
Vijay
3 Likes
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.
1 Like
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.
3 Likes
Hi all,
There’s a practical example using the new authentication method at https://hackernoon.com/robotic-process-automation-and-low-code-a-practical-tutorial-on-integrating-uipath-with-joget-b646bd2b96f2 in case you still have trouble authenticating.
Hope this helps!
4 Likes
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:
Second attempt:
Third attempt:
1 Like
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 https://orchestrator.uipath.com/v2019/reference#consuming-cloud-api 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.
3 Likes
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.
4 Likes
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.
1 Like
Could you check out this post of me for more reference on how to use the new Cloud API?
It contains a zipped project that will generate you all the necessary things. It is basically a project version of the guide from here:
https://orchestrator.uipath.com/v2019/reference#consuming-cloud-api
2 Likes
When I try to access the provided URL (https://platform.uipath.com/swagger/ui/index#/), it gives Account Not Found error. When I access the URL, it prompts login and then gives the error. However, if I just login to the account, there aren’t any such issues.
Could you kindly advise on this?
2 Likes
Please first navigate to your Orchestrator and then append this to the address:
/swagger/ui/index#/
Your link will look like so:
https://platform.uipath.com/yourCloudAccountName/yourOrchesteratorServicename/swagger/ui/index#/
3 Likes