Charset: [empty string]
ErrorDetail: I/O Exception: peer not authenticated
Filecontent: Connection Failure
Header: [empty string]
Mimetype: Unable to determine MIME type of file.
Responseheader: [struct]
Statuscode: Connection Failure. Status code unavailable.
Text: YES
After some Googling, it seemed that the remote server’s SSL certificate was not recognized by our server. Why all of a sudden and why now? We first thought there was a change in our server, OS, or firewall that was causing it. The remote server's certificate looked good. It was issued by Thawte, not a self-signed. So I asked the remote server admins. Apparently, Thawte, had changed the way they issued certificates and the new certs were not shipped with ColdFusion or the underlying Java. After digging around a bit on Thawte, I ran into this knowledge base article: https://search.thawte.com/support/ssl-digital-certificates/index?page=content&actp=CROSSLINK&id=AR1406. For Coldfusion or Java, read “Installation to a Java Keystore”. Then follow these steps:
- Copy the certificates in Step 1 of the knowledge base article and save them (e.g. in c:\ssl)
- Optional: Back up the folder/coldfusion9/jre/lib/security
- Open /coldfusion9/jre/lib/security from command prompt
- Issue the following command to install the first certificate (intca.cer). Note that keytool.exe is in another folder.
- It’ll prompt you to “Enter keystore password.” Enter “changeit” without quotes. “changeit” is the default password for cacerts
- You may prompted “Trust this certificate?” Enter “yes”
- You’re done when it says “Certificate was added to keystore”
- Check your keystore file size. It should have gone up by 1-2 KB (ours went from 67KB to 69KB).
\coldfusion9\runtime\jre\bin\keytool -import -trustcacerts -alias crossca -file c:\ssl\crossca.cer -keystore cacerts
- Check your keystore file size again. Ours went up to 70KB.

1 comment:
I'm still getting the "I/O Exception: peer not authenticated" error even after following your steps when trying to make a cfhttp call to https://api.dropbox.com am I missing something or is there something up with their cert?
Many thanks,
Chris
Post a Comment