You are viewing limited content. For full access, please sign in.

Question

Question

The request was aborted: could not create ssl/tls secure channel.

asked on October 15, 2018 Show version history

Hi All, I am trying to integrate Workflow with the TomTom (https://csv.telematics.tomtom.com/extern) HTTPS API as a web service. Yet Whenever I try to test/establish a connection I get an error "..could not create ssl.." as the title. The API only works with HTTPS not HTTP..

 

https://uk.support.telematics.tomtom.com/ci/fattach/get/3279534/1531821257/redirect/1/filename/WEBFLEET.connect%201.37.0-en-gb.pdf

 

0 0

Answer

SELECTED ANSWER
replied on October 14, 2020

Fixed yes

 

https://answers.laserfiche.com/questions/139438/LF-Workflow-HTTP-web-request-just-stopped-out-of-the-blue#167112

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:

  1. Start the registry editor by clicking on Start and Run. Type in "regedit" into the Run field (without quotations).

  2. 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.

  3. Browse to the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NetFramework\v4.0.30319

  4. Right-click on the right pane and create a new DWORD (32-bit) Value with Name SchUseStrongCrypto.

  5. Ensure that the Value data field is set to 1 and the Base is Hexadecimal. Click on OK.

  6. Repeat steps 4 and 5 for the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319

  7. Reboot the server

 

 

1 0

Replies

replied on October 15, 2018

I would guess it's the same error as https://answers.laserfiche.com/questions/139438/LF-Workflow-HTTP-web-request-just-stopped-out-of-the-blue#145217.  A tool like Wireshark could give you more insight as to what's not working.

1 0
replied on October 16, 2018

Thank you Brian, after much investigation the TLS version seems like the mostly likely culprit frown

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.