Failed to get authenicated via the Orchestrator API

Hello Team,

I’ve failed to get authenticated yet I see everything seems to be okay.
Kindly advise

Regards,
Kakooza Allan Klaus

@Kakooza-Allan-Klaus

Check below for your reference

Hope this will help you

Thanks

@Kakooza-Allan-Klaus - Based on the limited information, I would be interested in what you have configured in the Authorization Tab, as you should not be setting anything there for the initial authentication.

In the method you have approached it, it is as simple as

image

I would also verify in the External Applications section of the Cloud Portal that you have copied your Client ID, Secret, and Scope details appropriately.


You could then take it the next step and using the Tests tab, capture the access_token from the response and use pm.environment.set to assign it to a Environment Variable for use in other requests when setting your Authentication as a Bearer Token.

Alternatively in Postman you can set the Authorization on a Collection or Folder to OAuth 2.0 and it will handle getting your auth token and when needed the refresh.

In other Requests you set the Authorization to Inherit auth from parent.

1 Like

@codemonkee Thanks for your response
Below are the screenshots showing the adequate information needed.

For the External Application:

image

For the Authorization Body:

The error is still persisting.

KIndly advise.

You are actually showing a different error from your original “UnsupportedApiVersion” is not the same as “unauthorized_client”.

I would take the time to read over the documentation again, based on your External Application page screenshot, you are attempting to Authenticate for a Confidential Application which follows the Client Credentials Grant Type flow as describe in Accessing UiPath Resources Using External Applications.

In immediate post above, you are not using the correct URL of https://cloud.uipath.com/identity_/connect/token, but you did use it in your starting post.

In the last screenshot, you are using the wrong URL again, but also you need to decide how you are going to authenticate, As I mentioned in my reply above, if you are attempting to authenticate by passing the Key:Value pairs in the Body using x-www-form-urlencoded then you NEED to remove any authentication you have in the Authorization tab, you should not be attempting both in a single request to the token endpoint.

1 Like

I would also suggest not posting your authentication details, unless you are changing them after you’ve done your testing.

1 Like

Yeah I do change them after
Thank you
So what am I supposed to do here

Please Re-read both my posts above, they both have the same Information as well as read the documentation for more in-depth details (I linked directly to the section that pertains to your scenario)

  • Use the correct URL
  • Clear out any Auth Type in Authorization tab to No Auth UNLESS you are going to switch to using OAuth 2.0 in Postman in which case don’t call the authentication url directly. See first post with screenshots.
1 Like

So the correct is it the one that I was using in the first place.

And also clearing out my Authorization Tab to none. What do you mean exactly?

Kindly advise

In your screenshot you have the Authorization Type set to OAuth 2.0, change it to No Auth.

Okay @codemonkee
Initially I was using Bearer Token

You have two methods you can follow

  1. Authenticate against connect/token endpoint with the key:value pairs (Auth Type set to No Auth)
  2. Capture the Bearer Token from Auth request
  3. Make API request to desired endpoint set Auth Type to Bearer Token and provide the Key from Step 2.
  4. Refresh Token as/if needed

OR

  1. Make API request to desired endpoint, set Auth Type to OAuth 2.0. Postman will handle the token refresh if needed.

If you set OAuth 2.0 at the Collection or Folder level, you can set the Folder or Request so Auth Type Inherits from the Parent. Helpful when working with multiple endpoints

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.