401 Unauthorized - Invoke bot via API call
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-12-21 12:41 PM
Hi
Trying to invoke a bot which has been exposed as a SOAP API. I am using Basic Authentication, and the built-in "admin" user (who has sys admin role permissions). Also tried with another user who has Web Service Consumer role and can "Execute Process" and "Execute Process as Web Service". I keep getting this error - "HTTP POST on resource 'http://bp-trial:8181/ws/Sum2Proc' failed: unauthorized (401)."
I am using trial version 7.0.1.
Any suggestions as to what may be causing this error?
Any help much appreciated!
Thanks!
------------------------------
Yogesh Mudaliar
------------------------------
Trying to invoke a bot which has been exposed as a SOAP API. I am using Basic Authentication, and the built-in "admin" user (who has sys admin role permissions). Also tried with another user who has Web Service Consumer role and can "Execute Process" and "Execute Process as Web Service". I keep getting this error - "HTTP POST on resource 'http://bp-trial:8181/ws/Sum2Proc' failed: unauthorized (401)."
I am using trial version 7.0.1.
Any suggestions as to what may be causing this error?
Any help much appreciated!
Thanks!
------------------------------
Yogesh Mudaliar
------------------------------
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-12-21 09:07 PM
Hi @YogeshMudaliar,
What are you using to invoke the SOAP service? Are you writing custom code, using SoapUI, etc?
Cheers,
------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------
What are you using to invoke the SOAP service? Are you writing custom code, using SoapUI, etc?
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
09-12-21 01:00 AM
Hi @ewilson, thank you so much for your response. Appears to be an issue with the gui-based configuration. Switched over to manually passing the Authorization details in the request header and this works. All good now! 🙂
------------------------------
Yogesh Mudaliar
------------------------------
------------------------------
Yogesh Mudaliar
------------------------------
