- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-03-2022 07:51 PM
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".
Solved! Go to Solution.
- Labels:
-
IntegrationHub
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-15-2022 08:13 PM
[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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-08-2022 05:19 PM
Hi Richard
After obtaining the Client ID and Client Secret details from UiPath, we can successfully obtain an Access Token with a grant_type of client_credentials using both Postman and PowerShell.
We are unable to achieve the same from ServiceNow.
Even an explicit REST POST Message from ServiceNow (configured to mimic Postman and PowerShell) receives a "403 - Forbidden username/password combo" error from UiPath.
We're likely missing a header, or the content is not structured correctly, but we're not sure what or how.
FWIW, we can mimic the deprecated API Access method on ServiceNow using an explicit REST POST Message.
Regards
Katherine

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2022 01:14 AM
Katherine,
Forbidden username/password combo is an interpreted error message from ServiceNow.
It is likely that the action making the call needs a additional Authorization header.
If you can access the action in the spoke to update it, it will need to be similar to this:-
There is a space between Bearer and the value, the value is the Credential value from the credential alias.
If you cannot access the action to update it, you will need to engage the provider of the spoke to have them help you.
Thanks,
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-15-2022 08:13 PM
[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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-15-2023 08:04 PM
Hi Katherine6,
I am trying to configure UI path integration and unable to get Token with UI path spoke and With OAUTH Setup,Can you please help me with the steps for REsT integration