Christopher Stephens created JENKINS-13351: ----------------------------------------------
Summary: keystore specified in Jenkins startup is not used to make ssl call to crowd Key: JENKINS-13351 URL: https://issues.jenkins-ci.org/browse/JENKINS-13351 Project: Jenkins Issue Type: Bug Components: crowd2 Affects Versions: current Environment: debian squeeze jenkins 1.457 Reporter: Christopher Stephens Assignee: Thorsten Heit Priority: Minor I noticed that when I ran Jenkins under https and specified the keystore to use as per http://wiki.hudson-ci.org/display/HUDSON/Starting+and+Accessing+Hudson that I was unable to connect to our https instance of crowd. I verified that the keystore contained the correct certificates but testing the connection though jenkins always resulted in an ssl error. In order to get around this I had to specify the keystore path as a java argument: JAVA_ARGS="-Djavax.net.ssl.trustStore=/opt/etc/keystore -Djavax.net.ssl.trustStorePassword=*****" It appears that the crowd plugin is not using the credentials that are being used to start up winstone. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira