What to do now that UiPath Cloud are deprecating the API Access method provided by the UiPath Spoke.

Katherine6
Tera Expert

The configuration steps described on this page from UiPath are being deprecated: https://docs.uipath.com/automation-cloud/docs/about-api-access

Has anyone succeeded in configuring the necessary OAuth settings for the Spoke, as described on this page: https://docs.uipath.com/automation-cloud/docs/about-external-applications

Many thanks
Katherine

 

[Update from ServiceNow]

It has been determined the "User-Agent" value in the header needs to be explicitly set to "ServiceNow".

1 ACCEPTED SOLUTION

Katherine6
Tera Expert

[Update from ServiceNow]

It has been determined the "User-Agent" value in the header needs to be explicitly set to "ServiceNow".

Also seems my Google skills let me down, as I was unable to find this until today:
KB0720934 - Forbidden Username/password Combo error with Outbound Rest Call

View solution in original post

8 REPLIES 8

VaranAwesomenow
Mega Sage

I have seen similar issues with other cloud setup such as Hashicorp, their current version is like 3 to 4 years ahead of ServiceNow supported version, in that case we had to ask client teams to use objects that are compatible version supported by ServiceNow.

I believe in your case, you can raise an enhancement request and see if ServiceNow can include that in coming releases.

Richard Hine
Tera Guru
Tera Guru

Katherine,

I am not familiar with the spoke, but setting up 3rd part OAuth is pretty straightforward.

Create an OAuth application registration for third party (System OAuth -> Application Registry) 'New' Select 'Connect to a third party OAuth provider'.

Give it a name, populate the client ID and client secret supplied to you from UIPath team. You will likely want 'Client Credentials' as the grant type.

Populate the Token URL from the one provided by the UIPath team. (Optionally populate the same value into the Token Revocation URL).

Save the record, it should generate you a default record in the OAuth Entity Profiles related list. Make a note of this profile's name.

Switch to the OAuth Entity scopes related list, populate a list of scopes you will want to use with this OAuth provider. Update the record.

Create a new Credential (discovety_credentials.list) 'New' Select OAuth 2.0 Credentials. Give it a name and link it to the application registration using the OAuth Entity Profile from above.

Once that is saved, you should be able to use the 'Get OAuth Token' related link to retrieve a token. All being well and correctly configured it will confirm you now have a token. (You can check under System OAuth -> Manage Tokens).

Once you have a token you should be able to swap the new credential record you created to be the credential used by the connection for the spoke.

Hope this points you in the right direction,

Richard

Thanks for your input Richard

It should be as simple as this, but apparently not in this case.

Katherine,

Can you elaborate where you are finding complexity?

It might be that the grant type is different or something, but once you have the OAuth Token it should be relatively straightforward.

Happy to help where I can,

Richard