Webservice API for Oath2.0 not working for service now.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
27-11-21 01:37 PM
For generating the access token is perfectly working using postman when client_id, client_secret , username and password is provided.
In Blue prism it is showing as
Internal : Unexpected error Error during Web API HTTP Request
HTTP Status Code: 401
HTTP Response Content: {"error_description":"access_denied","error":"server_error"}
I created the following







I have passed client id, client secret , username and password correctly , But I am getting the below error in
blue prism

------------------------------
HMR
Developer
EY
Europe/London
------------------------------
In Blue prism it is showing as
Internal : Unexpected error Error during Web API HTTP Request
HTTP Status Code: 401
HTTP Response Content: {"error_description":"access_denied","error":"server_error"}
I created the following
I have passed client id, client secret , username and password correctly , But I am getting the below error in
blue prism
------------------------------
HMR
Developer
EY
Europe/London
------------------------------
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
28-11-21 07:25 PM
Hi @Hari MR,
Have you tried using the existing integration available on the Digital Exchange? It does exactly what you're trying to do.
From a quick glance at your screenshots, it doesn't appear that you're URL encoding your client ID, client secret, username, or password before trying to pass them along to ServiceNow.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
Have you tried using the existing integration available on the Digital Exchange? It does exactly what you're trying to do.
From a quick glance at your screenshots, it doesn't appear that you're URL encoding your client ID, client secret, username, or password before trying to pass them along to ServiceNow.
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
29-11-21 12:00 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
29-11-21 12:07 PM
@Hari MR,
I wasn't referring to the OAuth VBO. The link I provided above is to an existing asset on the Digital Exchange that implements ServiceNow authentication via their REST API. Have you tried that one?
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
I wasn't referring to the OAuth VBO. The link I provided above is to an existing asset on the Digital Exchange that implements ServiceNow authentication via their REST API. Have you tried that one?
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
29-11-21 04:53 PM
Hi Eric.
Thanks a Million!!!!!.
It worked like a charm.
I was trying all the possible methods and was not successful.
This helped me very much . Thanks again for your guidance.
------------------------------
Hari MR
Developer
EY
Europe/London
------------------------------
Thanks a Million!!!!!.
It worked like a charm.
I was trying all the possible methods and was not successful.
This helped me very much . Thanks again for your guidance.
------------------------------
Hari MR
Developer
EY
Europe/London
------------------------------
