SeanHoppe.com › EXTOL Errors › Failed to Send HTTP Request; No Trusted Certificate Found
Failed to Send HTTP Request; No Trusted Certificate Found
Scenario:
When trying to send data via EXTOL Secure the following error occured: No Trusted Certificate Found
Issue:
We are connection to Wells Fargo and their system requires HTTPS. For an HTTPS connection to occur in EXTOL Secure Exchange, we need the public SSL cert in ESX.
Error Message:
2015-06-11 17:25:02,320 Process INFO Established connection(Safetrans.wellsfargo.com:5000)
2015-06-11 17:25:02,320 Process ERROR Failed to send HTTP request(com.ibm.jsse2.util.g: No trusted certificate found)
2015-06-11 17:25:02,320 Process INFO Closed connection
2015-06-11 17:25:02,320 Process INFO Session delivery failed; waiting specified interval of 2 minutes before re-attempting to deliver
Resolution:
We requested the SSL public certificate from Wells Fargo SAFE Team. We imported the public cert into EXTOL Secure and that resolved the issue.
To set-up EXTOL Secure to re-send outbound AS2 data
- How-to set-up outbound channels in EXTOL Secure
- How-to resend outbound AS2 session from EXTOL Secure
By: Sean Hoppe on