> I then used the keytool and saved both the certificate and > the intermediate certificate. Bounced the CF server, still no joy. > > Very frustrating, I am still at square one.
I've been round this kind of merry-go-round before... In the past we (and when I say 'we', I really mean the infrastructure team): - Got a keytool browser and made sure that the certificate was in the keystore - Made sure that CF was looking at that keystore (there can be multiple AFAK) I'm flat out of ideas without sitting in front of the terminal, sorry :-/ <braindump> - You can definitely browse to the URL that CFHTTP is trying to call in your browser? - The URL is of the format https://ntpnow.com/whatever/whereever/ (Steven Erat's point)? - Imported the top level certificate (UTN-UserFIRST-Hardware) into the keystore? - Checked that other HTTPS calls are working okay using the same CFHTTP page? - Ensured that there is no firewall changes been made to your infrastructure that would maybe stop the CFHTTP call being made out by your server? </braindump> Soz man, can't think much else at the moment. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:254050 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
