Authenticate fails for Orchestrator API

Hi @Artem_Ibragimov

I realize it is a bit tricky to get started with the Cloud Platform API. The current guide is a temporary workaround given our migration to Auth0 (which removed the possibility to simply authenticate with basic authentication).

All the steps in this guide are unfortunately necessary. As far as concrete values in the guide, the variable ones are always between brackets []. This means that client_id should simply be taken as is and doesn’t need to be personalized.

However, if you do not feel like going through the entire guide, simply fire up the process attached in the below post that will do it for you:

Also, please keep in mind that all of this concerns only the Public Preview of our Cloud offering.
The on-premise installation of Orchestrator Enterprise still uses the standard basic authentication API, in which you simply call this endpoint and get a bearer token in return:

You can see the difference in documentation for both scenarios here:
image

EDIT
Last remark - after you go through all the steps and get your refresh_token, it is permanent. This means that afterwards you can make 1 api call to refresh your access_token without the need to go over all the steps again :slight_smile:

1 Like