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

Question

Question

The remote certificate is invalid according to the validation procedure

asked on December 23, 2016
Hello,
 
We have a client that is having an issue connecting Workflow and Forms to their Microsoft Exchange server. When we try to use SSL and send a test email through it, it gives the error "The remote certificate is invalid according to the validation procedure". Through working with Laserfiche support, we have verified that the certificate is a valid SSL certificate for the Fully Qualified Domain Name that is in use, and can be seen as valid through browsers on the server itself. We ran a .NET trace on workflow, and the .NET trace turns up the same error within .NET itself. Because of this, it seems that this is outside of Laserfiche and an issue with .NET itself.
 
We created a new Server 2012 Virtual Machine from scratch for testing purposes and installed workflow onto that server. We get the same issue there as well. Also interesting though is the same URL and settings are used for this client within SQL for SQL Reporting to send emails through, and it works just fine there.
 
Has anyone run across this error before and know what might be causing it?
0 0

Answer

SELECTED ANSWER
replied on January 11, 2017

Hi Brian,

 

Thank you for the insight. This didn't turn out to be the issue, as the certificate was a SHA2 cert.

 

We did figure out the cause however. For Workflow to be able to use the SSL certificate, we had to switch the port to use port 587 rather than port 25. Interestingly, other applications such as SQL Reporting were able to connect using SSL on port 25, which had thrown us off.

 

Thanks again!

0 0

Replies

replied on December 23, 2016

It's kind of a guess, but you may be running into SHA1 deprecation.  Some clients will see it as a valid certificate while others will not.

0 0
SELECTED ANSWER
replied on January 11, 2017

Hi Brian,

 

Thank you for the insight. This didn't turn out to be the issue, as the certificate was a SHA2 cert.

 

We did figure out the cause however. For Workflow to be able to use the SSL certificate, we had to switch the port to use port 587 rather than port 25. Interestingly, other applications such as SQL Reporting were able to connect using SSL on port 25, which had thrown us off.

 

Thanks again!

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

Sign in to reply to this post.