All geek questions in one place

Configuring Jenkins with StartSSL - Adding an Issuer Chain

I cannot properly configure Jenkins to use the StartSSL certificate. I run it with command line arguments that indicate the path to the private key and my certificate, as shown on the Jenkins wiki (below: https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins ) .

  • I got the private key and certificate from StartSSL
  • I placed them in a specific folder
  • I run Jenkins as follows: java -jar jenkins.war --httpPort=-1 --httpsPort=8080 --httpsCertificate=<mydomain.crt file> --httpsPrivateKey=<my private key file>

Jenkins starts successfully. The discovery https://mydomain:8080/in Firefox says the connection is not trusted:

mydomain:8080 uses an invalid security certificate.
The certificate is not trusted because no issuer chain was provided.
(Error code: sec_error_unknown_issuer)

I tried checking mydomain:8080on different sites SSL verification:

OK mydomain resolves to xxx.xxx.xxx.xxx

OK The certificate was issued by StartCom.  

OK The certificate will expire in XXX days. 

OK The hostname (mydomain) is correctly listed in the certificate.

Not OK The certificate is not trusted in all web browsers.
       You may need to install an Intermediate/chain certificate
       to link it to a trusted root certificate.

StartSSL Jenkins. StartCom (ca.pem sub.class1.server.ca.pem, : http://www.startssl.com/?app=42).

.

SSL-, www.sslshopper.com/ssl-checker.html, , . , GitHub Jenkins .

?

+4
1

, , :

: , merged.cer, , <my private key file>

Wiki Jenkins, KeyStore

    java -jar jenkins.war --httpPort=-1 --httpsPort=8080 --httpsKeyStore=/path/to/jenkins.jks --httpsPrivateKey=<my private key file>
+5

Source: https://habr.com/ru/post/1531785/

More articles:


All Articles