Error when using TLS encryption

Hi, I’ve been using 2019.2 for a while and the Create Email Content in PlanetPress Workflow worked well together with the option “Use encryption (TLS)” in the [Email Info]-tab.

I recently updated to a newer version (latest, 2021.2.3151).

Now when I try to use the same encryption I get this error message. Everything works well if i uncheck the “Use encryption (TLS)” checkbox.

Do you know what I have to do?

[0004] W3001 : Error while executing plugin: HTTP/1.1 500 Internal Server Error - An unspecified error occurred which was caused by ApplicationException: javax.mail.MessagingException: Could not convert socket to TLS;
nested exception is:
javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target (SRV000001)

Hi, you can solve the issue by installing the JRE certificat in directory C:\Program Files\Objectif Lune\OL Connect\jre\lib\security\cacerts.
You can search for file cacerts which by default could be installed in C:\Program Files (x86)\Java\jre1.8.0_xxx\lib\security
I hope this would help you.

Hi, I tried to but found that the complete jre folder is missing within the OL Connect folder. Should it be there? Should I copy the complete jre folder from Program Files?

Hi again, any update on this? Should the JRE be located in the OL Connect folder?

Another question: TLS 1.0 starting to be deprecated. When will PlanetPress Workflow be changed to TLS 1.2 or similar?

Hello,

Workflow was updated to use TLS 1.2 across the board or so close to a year ago in version 2021.1. Are seeing areas where this is still problematic ?

Hi,

Okay good! I have issues when I activate “Use encryption (TLS)” in the Create Email Content Properties, and I am trying to find out why it doesn’t work. Above someone said that I should copy the cacerts-file from JRE into the installation folder of Connect. That didn’t work.

So then i read your Workflow user guide and found out that it was TLS 1.0 that was used. Probably you updated the system but not the user guide?

I believe that the documentation is not up-to-date, that’s correct. I will open a work ticket to fix this. Thanks for pointing it out.