Question

LF Workflow HTTP web request just stopped out of the blue

Workflow Integrations

Updated October 14, 2020

asked on April 10, 2018

REST api calls to an outside site had been working fine, until 2 days ago at midnight now I get this every time

10/04/2018 3:57:56 PMHTTP Web RequestRequest failed with status code 500: SendFailure: The underlying connection was closed: An unexpected error occurred on a send..

10/04/2018 3:57:56 PMHTTP Web RequestThe underlying connection was closed: An unexpected error occurred on a send.

The api call looks like this

/api/2.0/B2C/Appointments?pagesize=300&startDate=%(DateTokenCalculator_Start_time#"MM//dd//yyyy h:mm:ss tt"#)&endDate=%(DateTokenCalculator_end_time#"MM//dd//yyyy h:mm:ss tt"#)

Because it stopped right at a date switch over I was thinking it could be related to date formatting somehow, but it has been working fine since last summer.

if I test with postman from the workflow machine the same call works perfectly fine, so it has to be a LF workflow issue.

I am at a loss of even where to start???

0 0

Answer

SELECTED ANSWER

replied on November 22, 2019

I finally found an answer that works

https://success.outsystems.com/Support/Enterprise_Customers/Maintenance_and_Operations/(.NET)_Enable_SSL_Protocols_for_your_Integrations_-_TLS_1.1_and_TLS_1.2

Use section B1

B1. Enable the SchUseStrongCrypto property in the Windows registry to use as the default protocols: TLS 1.0, TLS 1.1 and TLS 1.2

If you want to make sure strong cryptography is enabled and the SSL protocols for your requests to be TLS 1.0, TLS 1.1 and TLS 1.2, please follow this steps:

Start the registry editor by clicking on Start and Run. Type in "regedit" into the Run field (without quotations).
Highlight Computer at the top of the registry tree. Backup the registry first by clicking on File and then on Export. Select a file location to save the registry file.

Note: You will be editing the registry. This could have detrimental effects on your computer if done incorrectly, so it is strongly advised to make a backup.
Browse to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NetFramework\v4.0.30319
Right-click on the right pane and create a new DWORD (32-bit) Value with Name SchUseStrongCrypto.
Ensure that the Value data field is set to 1 and the Base is Hexadecimal. Click on OK.
Repeat steps 4 and 5 for the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319
Reboot the server

1 0

Replies

replied on April 11, 2018

So this ended up being that the API provider had dropped support for some old versions of TLS, I think 1.0

not sure if it was server 2008 r2 or laserfiche 10.1 but one way or another it wasn't supporting the newer TLS 1.2

0 0

View 1 previous reply

replied on July 21, 2018

So in my case I cheated and ran the api call through my Web filter gateway, but turned on https scanning which means it unencrypted the traffic at the gateway, and the gateway supported the older ssl still.

I would definitely raise a ticket though because there needs to be an official fix, because if I remember even a new install on server 2016 still had this issue.

0 0

replied on July 24, 2018

.Net 4 requires extra configuration for TLS 1.2 support. The steps are documented in KB article 1013919.

1 1

replied on September 26, 2018 • Show version history

I have a https web request in workflow that connects to QuickBooks online. QuickBooks depreciated TLS 1/1 on the 20th September accepting now only TLS 1.2 My workflow activity no longer works. Same error unable to establish secure connection SSL/TLS.

I have followed the Laserfiche KB article TLS 1.2 but still no connection. I captured the Post Request and it was still using HTTP 1.1

How can tell the workflow HTTP Web Request to use HTTP 1.2 requests?

0 0

replied on October 14, 2020

Thank you Joel, this worked for me as well.

0 0

You are not allowed to follow up in this post.

Question

Question

LF Workflow HTTP web request just stopped out of the blue

Answer

Replies

Sign in to reply to this post.