Orchestrator On-Prem - API Authentication not working with new password

I am experiencing a strange issue on our on-prem installation of Orchestrator when calling the /api/account/authenticate service.

The body of the request looks like this:

{
“tenancyName” : “MyTenant”,
“usernameOrEmailAddress” : “myapiuser”,
“password” : “NewPassword”
}

myapiuser is a new user account. I was able to log in to Orchestrator from a browser and then changed the initial password as I was expected to do by the Orchestrator.

Now, when trying to call the Authentication service I get this error message:

{
“message”: “Invalid credentials, failed to login.”,
“errorCode”: 1000,
“resourceIds”: null
}

If I change the Body and use the original password (the one before the password change) the authentication service works, but when log in to Orchestrator using this username, I need to use the new password.

Why are there 2 passwords for the same user? Why isn’t the password used for authentication from the API updated when I change the user’s password in Orchestrator?

1 Like

hi @ahorak
try this …

{
“TenancyName”: “MyTenant”,
“Username”: “myapiuser”,
“CurrentPassword”: “Password”,
“NewPassword”: “NewPassword”
}

I had the same issue and I was on call with UiPath. This is a known bug and they have given a work around. Go and reset the password once again from the profile page of the user. Then try and it should work. It works for me.

1 Like