topic RE: Blue Prism 6.10 Utility HTTP request in Product Forum

Blue Prism 6.10 Utility HTTP request

dhavaljp — Thu, 12 Aug 2021 13:44:00 GMT

Hi,

I was using 6.2 version and in that I use Utility HTTP request to call API. I use below configuration and it is working fine.

I migrated to 6.10 in that above configuration not give me result. I see blank collection from API.

I build this for companies house API.

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Thu, 12 Aug 2021 14:19:00 GMT

Hi @dhavaljp,

Can you provide some details about the make up of your Header collection? When you say you're seeing a blank collection from the API, what does that means? Which collection are you referring to? The action itself returns 2 strings (Result and Headers as JSON) and a number (Status Code).

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

dhavaljp — Thu, 12 Aug 2021 16:07:00 GMT

In headed I provide Authentication: ############.
This is result (as data item) in 6.10 ({"start_index":0,"items_per_page":25,"items":[],"filing_history_status":"filing-history-available","total_count":0})

while I run same in 6.2 I get this type of detailed result as data item ({"items_per_page":25,"filing_history_status":"filing-history-available","start_index":0,"items":[{"description":"miscellaneous","type":"MISC","date":"2019-04-12","category":"miscellaneous","description_values":{"description":"Confirmation of transfer of assets and liabilities"},"links":{"self":"/company/01378853/filing-history/MzIzMTk0ODM0N2FkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/Wki1Yf-Akcj6eFeYAT6apTm2LFvL2AfSFse0pTMIh3s"},"paper_filed":true,"pages":1,"barcode":"R838C37K","transaction_id":"MzIzMTk0ODM0N2FkaXF6a2N4"},{"links":{"self":"/company/01378853/filing-history/MzIzMTk0ODA4OGFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/zyyWVsHFbCja_AuG00ckXjuJ1TdeAD8IO1cIRbJQPUk"},"description_values":{"description":"Notification from overseas registry of completion of merger"},"paper_filed":true,"description":"miscellaneous","date":"2019-04-12","type":"MISC","category":"miscellaneous","pages":1,"barcode":"R81MT5OW","transaction_id":"MzIzMTk0ODA4OGFkaXF6a2N4"},{"type":"TM01","category":"officers","description":"termination-director-company-with-name-termination-date","date":"2019-01-07","links":{"self":"/company/01378853/filing-history/MzIyMzg1MzE5M2FkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/DR73UOIeUkOyUxYxKvxiE5-oHY29YAzCCq1sLDX8048"},"description_values":{"officer_name":"Jonathan Wyn Parry","termination_date":"2018-12-31"},"subcategory":"termination","action_date":"2018-12-31","pages":1,"barcode":"X7WMDI9L","transaction_id":"MzIyMzg1MzE5M2FkaXF6a2N4"},{"subcategory":"termination","action_date":"2018-12-31","description_values":{"termination_date":"2018-12-31","officer_name":"Wai-Fong Au"},"links":{"self":"/company/01378853/filing-history/MzIyMzg1MzIyMmFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/5ZTYhZnl1chdepPOQtyhP7_PYba2cT4eWuJjatDQHtQ"},"date":"2019-01-07","description":"termination-director-company-with-name-termination-date","type":"TM01","category":"officers","pages":1,"barcode":"X7WMDI7L","transaction_id":"MzIyMzg1MzIyMmFkaXF6a2N4"},{"category":"officers","type":"TM01","description":"termination-director-company-with-name-termination-date","date":"2019-01-07","links":{"self":"/company/01378853/filing-history/MzIyMzg1MzIyMGFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/iDrjVEtP74gn444gfH4WLxzXKYO5_RabOAtEX2-cDEM"},"description_values":{"officer_name":"Stuart William Sinclair","termination_date":"2018-12-31"},"action_date":"2018-12-31","subcategory":"termination","pages":1,"barcode":"X7WMDI5D","transaction_id":"MzIyMzg1MzIyMGFkaXF6a2N4"},{"date":"2018-09-19","description_values":{"description":"CB01 - cross border merger notice"},"description":"miscellaneous","type":"MISC","paper_filed":true,"category":"miscellaneous","links":{"self":"/company/01378853/filing-history/MzIxNDg2NjM1N2FkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/m5rkmHXiMTMhLfAjAs21uFD5GEF6Gd0jeU87JJBnHiI"},"pages":42,"barcode":"L7EI4K88","transaction_id":"MzIxNDg2NjM1N2FkaXF6a2N4"},{"action_date":"2018-06-29","category":"confirmation-statement","date":"2018-07-09","description_values":{"made_up_date":"2018-06-29"},"description":"confirmation-statement-with-no-updates","links":{"self":"/company/01378853/filing-history/MzIwOTM0MDgxNmFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/Svricwk_YSlOVTJDX_fkSoCJusW5tdpAK8CN3NxwCEM"},"type":"CS01","pages":3,"barcode":"X79UFZJE","transaction_id":"MzIwOTM0MDgxNmFkaXF6a2N4"},{"links":{"self":"/company/01378853/filing-history/MzIwNDIxMjk2M2FkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/jUAoan4GG4QrxG0QclPafpsKcxMJwj4Vy6GJJBU4TQc"},"subcategory":"change","description_values":{"officer_name":"Mr Malcolm Graham Mccaig","change_date":"2018-04-27"},"category":"officers","type":"CH01","action_date":"2018-04-27","date":"2018-05-03","description":"change-person-director-company-with-change-date","pages":2,"barcode":"X75526E4","transaction_id":"MzIwNDIxMjk2M2FkaXF6a2N4"},{"links":{"self":"/company/01378853/filing-history/MzIwNDIxMjg3M2FkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/2f0yegTYfXez_m8Eqt4Flu-b2mRAa1pAXewPsFGM8_E"},"subcategory":"change","category":"officers","description_values":{"officer_name":"Mr Malcolm Graham Mccaig","change_date":"2018-04-27"},"action_date":"2018-04-27","type":"CH01","description":"change-person-director-company-with-change-date","date":"2018-05-03","pages":2,"barcode":"X75524CQ","transaction_id":"MzIwNDIxMjg3M2FkaXF6a2N4"},{"description_values":{"made_up_date":"2017-12-31"},"description":"accounts-with-accounts-type-full","type":"AA","category":"accounts","paper_filed":true,"date":"2018-03-21","links":{"self":"/company/01378853/filing-history/MzIwMDU5NzU2MWFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/5g9PRXeGodZVXM4S8PIBOG3SaXzBs3NJ51RSoyN27S4"},"action_date":"2017-12-31","pages":49,"barcode":"A71WZ402","transaction_id":"MzIwMDU5NzU2MWFkaXF6a2N4"},{"action_date":"2016-12-31","description_values":{"made_up_date":"2016-12-31"},"type":"AA","description":"accounts-with-accounts-type-full","links":{"self":"/company/01378853/filing-history/MzE4MzA5MzI0NmFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/cBqsOXKnJnCjXBO3AU5CzYbp5ikAL1J8ee_leqDIpw4"},"paper_filed":true,"category":"accounts","date":"2017-08-17","pages":46,"barcode":"A6CIR156","transaction_id":"MzE4MzA5MzI0NmFkaXF6a2N4"},{"description":"confirmation-statement-with-updates","type":"CS01","description_values":{"made_up_date":"2017-06-29"},"links":{"self":"/company/01378853/filing-history/MzE4MDQwMzM1M2FkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/dDwU58yB_2m7jEiKoWmOMI8MfXzz8duraO_jx3Rztbk"},"category":"confirmation-statement","action_date":"2017-06-29","date":"2017-07-12","pages":4,"barcode":"X6AJFSAX","transaction_id":"MzE4MDQwMzM1M2FkaXF6a2N4"},{"description":"notification-of-a-person-with-significant-control","type":"PSC02","description_values":{"psc_name":"Qbe Holdings (Eo) Limited","notification_date":"2016-04-06"},"subcategory":"notifications","links":{"self":"/company/01378853/filing-history/MzE4MDM5NzQyMGFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/qOavj1kdudV9n-i1MP1H6jQHGa_73VVDVViwhvcVNfE"},"category":"persons-with-significant-control","action_date":"2016-04-06","date":"2017-07-12","pages":2,"barcode":"X6AJ7ZVE","transaction_id":"MzE4MDM5NzQyMGFkaXF6a2N4"},{"action_date":"2017-06-26","links":{"self":"/company/01378853/filing-history/MzE3OTI5ODI1NGFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/qpdAvOv2OTzTo3oU7fXInywMISfHTPHJ9F9-7MXsZJY"},"type":"AP03","subcategory":"appointments","date":"2017-06-29","category":"officers","description_values":{"appointment_date":"2017-06-26","officer_name":"Alexandra Jane Smith"},"description":"appoint-person-secretary-company-with-name-date","pages":2,"barcode":"X69L03JC","transaction_id":"MzE3OTI5ODI1NGFkaXF6a2N4"},{"links":{"self":"/company/01378853/filing-history/MzE3OTI5NjExMWFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/dQqazz7kz52JJt5U8RmjbTMEMf6UYiwA4XdOeC2Onw4"},"type":"TM02","action_date":"2017-06-26","date":"2017-06-29","subcategory":"termination","category":"officers","description_values":{"termination_date":"2017-06-26","officer_name":"Esther Felton Smith"},"description":"termination-secretary-company-with-name-termination-date","pages":1,"barcode":"X69KXE6Y","transaction_id":"MzE3OTI5NjExMWFkaXF6a2N4"},{"subcategory":"appointments","description_values":{"officer_name":"Mr Nigel Joseph Douty Terry","appointment_date":"2016-12-19"},"date":"2016-12-23","description":"appoint-person-director-company-with-name-date","category":"officers","type":"AP01","action_date":"2016-12-19","links":{"self":"/company/01378853/filing-history/MzE2NTE1NTA5MGFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/gXtpVjxf_DpwujTR3saghgZSfa_u7Y02tbppf7FE8RM"},"pages":2,"barcode":"X5MDJTNM","transaction_id":"MzE2NTE1NTA5MGFkaXF6a2N4"},{"date":"2016-12-22","description_values":{"officer_name":"Philip Andrew Dodridge","termination_date":"2016-12-19"},"description":"termination-director-company-with-name-termination-date","subcategory":"termination","action_date":"2016-12-19","type":"TM01","links":{"self":"/company/01378853/filing-history/MzE2NTE1NTA3MGFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/CIeBJd-D4nT9T3fS1-sdZQzuNVFLKAB3Pn-QadRBp_4"},"category":"officers","pages":1,"barcode":"X5MDJTOA","transaction_id":"MzE2NTE1NTA3MGFkaXF6a2N4"},{"links":{"self":"/company/01378853/filing-history/MzE1OTA3NDQwNWFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/jnv7spePfcU9AQeKd3-uD9DRVcIxKOtg71rt2_969MA"},"date":"2016-10-06","description":"change-person-director-company-with-change-date","category":"officers","description_values":{"change_date":"2016-07-19","officer_name":"Mr Malcolm Graham Mccaig"},"subcategory":"change","type":"CH01","action_date":"2016-07-19","pages":2,"barcode":"X5H1MDJ6","transaction_id":"MzE1OTA3NDQwNWFkaXF6a2N4"},{"associated_filings":[{"action_date":1468195200000,"category":"capital","date":"2016-07-11","description":"statement-of-capital","description_values":{"capital":[{"currency":"GBP","figure":"20,082,852"}],"date":"2016-07-11"},"type":"SH01"}],"type":"AR01","links":{"self":"/company/01378853/filing-history/MzE1MjY1NjQwMWFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/HKDP56btbCgV2awXAIon8f7aeH5veEGcxiwyiT73yVI"},"date":"2016-07-11","description":"annual-return-company-with-made-up-date-full-list-shareholders","action_date":"2016-06-29","description_values":{"made_up_date":"2016-06-29"},"category":"annual-return","pages":8,"barcode":"X5B07I1K","transaction_id":"MzE1MjY1NjQwMWFkaXF6a2N4"},{"category":"accounts","description_values":{"made_up_date":"2015-12-31"},"paper_filed":true,"type":"AA","action_date":"2015-12-31","date":"2016-05-11","description":"accounts-with-accounts-type-full","links":{"self":"/company/01378853/filing-history/MzE0ODIxNDkyMGFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/9LzU83Y6TTcJpmEzJmNRh9CjQps2-bcpOQJxl0ta7JQ"},"pages":45,"barcode":"A56FHZ2Z","transaction_id":"MzE0ODIxNDkyMGFkaXF6a2N4"},{"description_values":{"made_up_date":"2015-06-30"},"date":"2015-07-22","action_date":"2015-06-30","links":{"self":"/company/01378853/filing-history/MzEyNzU0MDIyMmFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/4Gm6iPnibvE4Cfa81T-mjN51gM1fiG_ATATsAnRSd10"},"type":"AR01","category":"annual-return","description":"annual-return-company-with-made-up-date-full-list-shareholders","associated_filings":[{"action_date":1437523200000,"category":"capital","date":"2015-07-22","description":"statement-of-capital","description_values":{"capital":[{"currency":"GBP","figure":"20,082,852"}],"date":"2015-07-22"},"type":"SH01"}],"pages":9,"barcode":"X4C6QDE4","transaction_id":"MzEyNzU0MDIyMmFkaXF6a2N4"},{"action_date":"2015-06-29","links":{"self":"/company/01378853/filing-history/MzEyNjk2NTQxOWFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/tX7lVubuRpw6rzDQP08F1bsmDh6hPQ7MUbd3oAm1yQ8"},"description":"termination-director-company-with-name-termination-date","date":"2015-07-13","category":"officers","subcategory":"termination","type":"TM01","description_values":{"officer_name":"Joe Gordon","termination_date":"2015-06-29"},"pages":1,"barcode":"X4BJA83N","transaction_id":"MzEyNjk2NTQxOWFkaXF6a2N4"},{"action_date":"2015-06-29","links":{"self":"/company/01378853/filing-history/MzEyNjk2NTQyMmFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/XkVyROZavlG2jJlgtD_YMRXU1zfVNut9ZDcHxLEzK4Q"},"description":"termination-director-company-with-name-termination-date","date":"2015-07-13","category":"officers","type":"TM01","subcategory":"termination","description_values":{"termination_date":"2015-06-29","officer_name":"Dominic John Clayden"},"pages":1,"barcode":"X4BJA87U","transaction_id":"MzEyNjk2NTQyMmFkaXF6a2N4"},{"date":"2015-07-13","description":"termination-director-company-with-name-termination-date","action_date":"2015-06-29","links":{"self":"/company/01378853/filing-history/MzEyNjk2NTQxOGFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/f04G1Pw7xhVJ7yyttIRjhLL07sL5kHcobPKGyM5SKUI"},"subcategory":"termination","type":"TM01","description_values":{"officer_name":"Ian David Beckerson","termination_date":"2015-06-29"},"category":"officers","pages":1,"barcode":"X4BJA7XK","transaction_id":"MzEyNjk2NTQxOGFkaXF6a2N4"},{"description_values":{"officer_name":"Jan Leflot","termination_date":"2015-06-29"},"subcategory":"termination","type":"TM01","category":"officers","date":"2015-07-13","description":"termination-director-company-with-name-termination-date","links":{"self":"/company/01378853/filing-history/MzEyNjk2NTQxNWFkaXF6a2N4","document_metadata":"https://frontend-doc-api.company-information.service.gov.uk/document/znYarw9dMQWTezUn1MvEgnuWcpbBmCsQZGjVK9hmpcw"},"action_date":"2015-06-29","pages":1,"barcode":"X4BJA89E","transaction_id":"MzEyNjk2NTQxNWFkaXF6a2N4"}],"total_count":281})

I store API result in data item and then convert that JASON to collection. but in 6.10 there is no record collection shows blank.

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Thu, 12 Aug 2021 17:52:00 GMT

Ok, so one thing I see right off is that you're setting your Accept request header to Application/pdf, but the result data is JSON. If you expect to receive JSON you should be setting Accept to application/json. The fact that you're getting back some JSON shows that the request is actually making it to the server. I would verify the authentication credential you're passing in to be sure it's the same between your 6.2 and 6.10 environments. Even a single white-space character at the end or beginning of the auth info can cause it to fail in which case could cause your server to not respond with the data you expect.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

dhavaljp — Thu, 12 Aug 2021 18:15:00 GMT

I changed it json but still not working. For some company I get correct output but its very rare. so I guess no issue for authentication. Is there any major change in HTTP request between 6.2 and 6.10? Chrome version also updated for 6.10.

for few case get the result then why I am not getting for all cases like 6.2?

Please let me know any further details require.

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Fri, 13 Aug 2021 12:34:00 GMT

I don't have a copy of the v6.2 VBO, so I can't compare/contrast. However, you have both so you can see what's in the code stage of both VBOs on the HTTP Request action. I'm guessing there are some changes, but I'm highly skeptical of anything in the VBO causing the issue you're seeing when you telling me sometimes things work fine. Sometimes they don't.

Going back to the auth header. Have you actually titled the header Authentication or is it Authorization? The HTTP basic auth header should be Authorization (ex. Authorization: Basic [Base64 encoded username:password]).

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

dhavaljp — Fri, 13 Aug 2021 18:35:00 GMT

Hi Wilson,
its authorization, it was my mistake. I attached file of both code comparison. is there any browser setting require for api access.

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Sat, 14 Aug 2021 01:51:00 GMT

@dhavaljp,

It looks like there was a small bug in the handling of Authorization headers when you pass one in as part of the Headers collection. There is a parameter on the VBO called Force Pre Authorization that was designed to be used with the Username and Password parameters to handle HTTP Basic Authorization. In other words, the expectation was that you would set that Flag to True and populate the Username and Password values. Then we build the Authorization header for you, in the code.

We've uploaded a update to the HTTP VBO to the Digital Exchange. I'd suggest downloading the latest copy and see how that works for you.

In the revised version, priority is given to use of the Force Pre Authorization flag, followed by the Use Bearer Token flag (this is another option for the Authorization header), and finally any Authorization header included in the input Headers collection. To be clear, a web server will only look at the very first Authorization header it receives. All others should be ignored. So my recommendation is that you use the Force Pre Authorization flag in conjunction with the Username and Password parameters. If that's not possible, then you can stick with passing in your header within the Headers collection.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

dhavaljp — Sun, 15 Aug 2021 12:22:00 GMT

What is username and password for Force Pre Authorization.

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Sun, 15 Aug 2021 13:04:00 GMT

Hmm. Let's go back to the beginning a bit. You said you were passing in a header called Authorization within the Headers collection. Did you create the value of that header, or did you just pull it from somewhere? Do you know if the service you're invoking is HTTP Basic auth or Bearer auth?

In an HTTP Basic auth situation the value of the Authorization header is a string made up of the word Basic and the Base64 encoded output of whatever username and password you server expects (concatenated together with a : (colon).

Here's an example of the value of the Authorization header in an HTTP Basic scenario with username jdoe and password 123pass:

Basic amRvZToxMjNwYXNz

Now, if the server you're connecting to is expects Bearer token authorization, the value of your header would be the word Bearer combined with the token string (bearer tokens are not Base64 encoded typically). Here's an example with a token value of RsT5OjbzRn430zqMLgV3Ia.

Bearer RsT5OjbzRn430zqMLgV3Ia

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

dhavaljp — Sun, 15 Aug 2021 13:55:00 GMT

Hi Eric,

I downloaded updated VBO from this link. https://digitalexchange.blueprism.com/dx/entry/3439/solution/utility---http
By using this new vbo I face same issue. First time I received output after that don't receive require output.
I don't understand what should be given as username and password with force pre authorization. I try with system username and password but its fail.
Can it be work like 6.2 version where no username password require.
When i use normal header i got error as " m_certificate variable is not declared and it is inaccessible due to its protection level" so i commented those lines in code but then it gives me error that "Proxy authentication required"

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

dhavaljp — Sun, 15 Aug 2021 14:06:00 GMT

I use API key which I got from companies house website. this is my header looks like.
with same details it work in 6.2. while in 6.10 it work only first time and then don't work.

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Sun, 15 Aug 2021 14:43:00 GMT

The screenshot below is from the Companies House site describing API authentication. You can find the page here.

According to that page they use the HTTP Basic scheme with your API key being passed in as the username value. They ignore the password. So, try setting Force Pre Authorization to True and set Username to the value of your API key. You should be able to leave Password blank.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

dhavaljp — Sun, 15 Aug 2021 15:23:00 GMT

Hi Eric,

I already tried with option you suggested.

Even I try with header as well. but getting below error.

<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Access Denied (authentication_failed)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
<h2>Sorry, your access has been denied</h2>We're sorry, your access to the Intranet has been denied because the username and password you entered does not match our records. Please try these suggestions for entering the correct username and password:<br/><br/><h3>Did you enter the right username?</h3>Your user name should be all lower-case letters (with no spaces between the first and last name), for example, john_brown.<h3>Still not working? <a href=http://simpleaccess20.mhf.mhc/xlWebApp/forgetPassword.do?method=displayVerifyUserId target=_top>Click here</a> to reset your password by the "Forgotten Password" link. You will be required to have your answers to the previously selected secret questions.</h3>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">

</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
<BR>
For assistance, please contact <BR><BR>S&P Global Service Desk # contact no., or find the full global list on theHub <BR><BR>As an alternative to calling Service Desk, you can submit your service request easily on our eHelp site at <a href=http://ehelp.mhf.mhc>http://ehelp.mhf.mhc</a> or send an email to. ################
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Sun, 15 Aug 2021 16:00:00 GMT

@dhavaljp,

You mentioned Companies House. Are you aware there's an existing integration for Companies House on the DX. Have you tried that connector?

I just performed a Search Companies call against the Companies House API, using my API key and the latest HTTP VBO, and I received results just fine.

The response you show above seems to imply that you're working through a proxy server. Is that the case? If so, you would typically need to set the Use Proxy flag and the Proxy URI, Proxy Username, and Proxy Password values too.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

dhavaljp — Sun, 15 Aug 2021 18:37:00 GMT

Thanks Eric for your time to resolve this issue.

I build bot to fetch PDF files from companies house, its not available in current digital exchange API. Even I check with that API, I got below error.

Internal : Unexpected error Error during Web API HTTP Request
HTTP Status Code: 400
HTTP Response Content: {"error":"Invalid Authorization header","type":"ch:service"}

I downgraded my BP version to 6.2 and run the bot it working fine on same machine where I am facing issue in 6.10. Is there any setting require for web api in BP?

Kindly recheck your Utility HTTP request code that looks main issue.

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Sun, 15 Aug 2021 20:35:00 GMT

@dhavaljp,

If you're saying your HTTP VBO from v6.2 does exactly what you need, why don't you import that VBO into your v6.10 environment and use it?

To investigate the v6.10 VBO further I'll need more information regarding what specific endpoints on the Companies House API you're trying to invoke, so I can build a test process that replicates exactly what you're doing (or as close to it as possible). You mention you're downloading PDF's, can I assume that you means you're trying to use the Companies House Document API? If so, can you send me the specific document_id that you're trying to download?

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Sun, 15 Aug 2021 21:16:00 GMT

@dhavaljp,

I added a few steps to my current test including fetching a PDF of an AD02 filing by Blue Prism. It worked fine for me.

NOTE: To download a binary file like a PDF you should use the HTTP Request File action, instead of the HTTP Request action. This will capture the binary stream and actually write it to a file on your local drive.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

dhavaljp — Mon, 16 Aug 2021 10:02:00 GMT

I import 6.2 VBO in 6.10, in that case I received this error. "Could not execute code stage because exception thrown by code stage: The remote server returned an error: (407) Proxy Authentication Required."
Are you provide only API key as username or anything else needs to be provide with it?
Like: api keys is: 9bf911c4-91e6-43cd-a463-06####### then provide only API key?
I use below code to fetch document.

------------------------------
Dhaval Panchal
Senior Data Researcher II
S&P Global
------------------------------

RE: Blue Prism 6.10 Utility HTTP request

ewilson — Mon, 16 Aug 2021 12:56:00 GMT

@dhavaljp,

If you recall earlier in our thread you had received a 407 HTTP response page, and I asked if you were working through a web proxy on your company network. This seems to show that you are indeed working through a proxy server. When you open a normal browser window and browse to a web site (ex. this Community site) are you prompted to enter credentials first? Most likely, your proxy server requires your network credentials (typically the same credentials you use when you log into your machine).

The VBO exposes four parameters that should be set if you are traversing a proxy server: Use Proxy, Proxy URL, Proxy Username, and Proxy Password.

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------