I am trying to write a Node.js code to call orchestrator API for Authentication. I am getting the below error,
Response: {“message”:“loginModel must not be null”,“errorCode”:0,“resourceIds”:null}
any help is really appreciated.
==============Node.js Code====================
var http = require(‘https’);
exports.handler = function(event, context){
Running “https://platform.uipath.com/api/Account/Authenticate” in postman and getting the same error
{
“message”: “loginModel must not be null”,
“errorCode”: 0,
“resourceIds”: null
}
Is there any fix for this?
We are trying to connect to on premise Orchestrator API from OSB Middleware and getting this error. We are able to connect using Postman as well as Python script. Any solutions?
I have the same issue, unable to autenticate via Swagger or Postman
Same error:
{
“message”: “loginModel must not be null”,
“errorCode”: 0,
“resourceIds”: null
}
I am working on an On-Premise orchestartor and I can access it just fine.
However, I fail to even authenticate using APIs
I got this solution for UiPath community Orchestrator from UiPath, Well I was not able to authenticate using this method also.
But if you might try now it might work.
I am setting my headers as in the docs and the body includes those three things:
{
“grant_type”: “refresh_token”,
“client_id”: “8DEv1AMNXczW3y4U15LL3jYf62jK93n5”,
“refresh_token”: “my refresh token value”
}
In some cases you may need to escape quotation marks.
So, instead of writing { “tenancyName”: “string”, … }
try { \“tenancyName\”: \“string\”, … }
That fixed the “loginModel must not be null” issue for me when I made requests to the Orchestator API with curl on Windows Command Prompt. If you’re using PowerShell, the same fix works. Though, you may need to do Remove-item alias:curl first, so that curl is used instead of Invoke-WebRequest.