CAS proxy validation failure - Configured TLS trust engine was not used

Cantor, Scott cantor.2 at
Mon Aug 17 12:17:27 UTC 2020

On 8/16/20, 11:29 PM, "users on behalf of Paul B. Henson" <users-bounces at on behalf of henson at> wrote:

>    Any thoughts on what's going on here?

The error generally refers to a misconfigured HttpClient that's not set up with the proper socket factory so that the trust engine used to verify the certificate is actually enforced. It's a sanity check against misconfiguration because of the complex way the TLS verification has to be done.

The default clients are set up with the intended socket factory, but custom clients are obviously custom.

-- Scott

More information about the users mailing list