Closed menudrive-mylesb closed 5 years ago
@menudrive-mylesb We have a ticket out to an internal team to get the certificate updated on api2-c.heartlandportico.com.
Thanks @slogsdon
@menudrive-mylesb Which version/URL of the library are you currently using? Version 2.2.1 (the latest), which uses the api2-c.heartlandportico.com domain, only updated the domain when compared 2.2.0. Leveraging the 2.2.0 version of the library should side-step this issue while our teams get the certificate updated.
Using the latest (2.2.1), will give 2.2.0 a shot, thanks!
Older version uses a domain that has the newer wildcard cert and appears to work just fine, closing this issue as it's essentially resolved until the ticket with another team can be resolved
@menudrive-mylesb Thanks for the update!
See #51, @slogsdon @russelleverett is there any way you can reach out to the ops team or whoever is in charge of this and have them get a certificate issued by someone other than Symantec? It is now untrusted by both Mozilla and Google in the latest versions of FF/Chrome. See: https://www.ssllabs.com/ssltest/analyze.html?d=api2-c.heartlandportico.com