Highlighted

Schedule tasks not working for SSL.

New Here ,
Jan 13, 2015

Copy link to clipboard

Copied

I am running CF11 using Tomcat 7 and jdk1.7.0_45.  I have non-SSL sites that execute the exact same task fine.  However for my SSL enabled sites, the task will not run.  Does anyone have an idea as to what is causing this?

Views

393

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Schedule tasks not working for SSL.

New Here ,
Jan 13, 2015

Copy link to clipboard

Copied

I am running CF11 using Tomcat 7 and jdk1.7.0_45.  I have non-SSL sites that execute the exact same task fine.  However for my SSL enabled sites, the task will not run.  Does anyone have an idea as to what is causing this?

Views

394

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jan 13, 2015 0
Guide ,
Jan 13, 2015

Copy link to clipboard

Copied

Perhaps you need to add the SSL certificate to the CF Java keystore? EG

d:\Program Files\Java\jdk1.7.0_45\jre\bin>
keytool -importcert -storepass changeit -noprompt -alias friendly_name -keystore
..\lib\security\cacerts -trustcacerts -file d:\temp\sslcertificate_file.cer

I understand CF11 is using JRE in 1.7.0_45, check CFadmin i system information. CF will require a restart to re-read change to trusted keystore.

HTH, Carl.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 13, 2015 0
Advocate ,
Jan 13, 2015

Copy link to clipboard

Copied

I can confirm that cfschedule does work with SSL and yes you will need to import the certificate or root certificate into your certificate store if it is not one issued by a "well known" provider that the jre supports. The gotcha is that the certificate domain must match the server name used in the cfschedule call. For us this meant that our www.domain.com cert did not work, even after importing, for https://127.0.0.1/... To fix this we created a hosts file entry so the request didn't have to round trip outside the box.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 13, 2015 0