UiPath.WebApi 12.0 - Orchestrator authentication deprecated

Help Orchestrator
, , ,
1

Hi all , I see that this method:

deprecated
deprecated1283×572 18.3 KB

has been deprecated when it comes to authenticating user in order to use Orchestrator APIs.

  1. Is it deprecated for both cloud and on premise orchestrator ?
  2. I just used it and worked on postman( i got the access key in my response) but I dont want to risk continuing to use it and then later I have to change it once it is cut off, any clue when it will be stopped for on-premise Orchestrator ?
  3. Can I continue using this ?

Thanks

2

When working with cloud Orchestrator you’d better use this endpoint:

https://account.uipath.com/oauth/token

image

Avalability of former endpoint in On-Premise Orchestrator will depend on your upgrading plans for that installation.

3

Thanks for getting back to me @dokumentor , I am using on-premise orchestrator , do you suggest , I continue using the on on the screenshot that I sent?

What do you mean by it will depend on upgrading plans for orchestrator ?

5

As I can see method deprecated is NTLM:

image
image811×302 13.7 KB

OAuth Authentication is the recommended:

https://docs.uipath.com/orchestrator/reference/using-oauth-for-external-apps

6

Some additional helpful references. Afaik Basic Auth has not been publically depricated yet, but NTLM has. OAuth for External Applications for On-Prem is available as of 2021.4

https://docs.uipath.com/orchestrator/reference/authenticating

2 Likes
7

Meaning , I can continue using this method

deprecated
deprecated1283×572 18.3 KB

for on-premise ?

8

In the moment yes with both Basic and NTLM. But be aware that NTLM has already been depricated and I wouldn’t be surprised if the authentication endpoint or basic auth is also depricated within the next few major releases.

As noted above, OAuth is preferred and where authentication is heading if you want to stay ahead of the game.

1 Like