[
https://issues.jenkins-ci.org/browse/JENKINS-11673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161825#comment-161825
]
Yury Zaytsev commented on JENKINS-11673:
----------------------------------------
Hi,
Thanks for clarifying. I don't think this gonna help though, really. You also
need to generate the key and provide the path to the key and keystore password.
So if you automate those steps in the SPEC file, then it would totally make
sense to add such an option, because it will just work.
FYI, I used the following commands (generates a self-signed certificate valid
for the next 10 years):
{code}
keytool -genkey -keyalg RSA -alias selfsigned -keystore
/var/lib/jenkins/ssl/keystore.jks -validity 3650 -dname "cn=FQDN" -storepass XXX
{code}
The FQDN can be determined via {code}hostname -f{code}.
The command to use HTTPS is
{code}
--httpsPort=443 --httpsKeyStore=/var/lib/jenkins/ssl/keystore.jks
--httpsKeyStorePassword=XXX
{code}
Also it would make sense to add an option to disable AJP port:
{code}
--ajp13Port=-1
{code}
If you will make a working patch, I can try to help to make a pull request,
unless you can also do it yourself.
> Support https in RPM service scripts
> ------------------------------------
>
> Key: JENKINS-11673
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11673
> Project: Jenkins
> Issue Type: Improvement
> Components: core
> Reporter: teilo
> Assignee: teilo
> Priority: Minor
>
> It would be nice if the RPM allowed you to simply configure https as well as
> http
--
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
