Jenkins
Space shortcuts
Child pages
  • Skip Certificate Check plugin

Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
  • Created by Unknown User (kohsuke), last modified by Unknown User (lshatzer) on Aug 05, 2013
Go to start of metadata

This is a plugin that makes JVM bypass all the HTTPS certificate checks. Convenient if you deal with self-signed certificates and so on. Use with caution.

Plugin Information

View skip-certificate-check on the plugin site for more information.

Usage

This plugin doesn't require any configuration. It activates itself when Jenkins starts.

Changelog

Version 1.1 (upcoming)

Version 1.0 (Sep 7th 2011)

  • initial version

5 Comments

  1. Unknown User (sodul)

    I tried the plugin to have the Jira plugin connect to a self signed Jira instance and I still get this error, even after restarting Jenkins:

    javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

    We are using jdk1.6.0_41 and Jenkins 1.515.

    1. Unknown User (vicd)

      Same here. Debian Squeeze + Oracle JDK 7 + Jenkins 1.549 + this plugin + JIRA with no intermediate/root CA certificates, just the last-in-chain one. The jenkins config page throws the following exception when trying to configure JIRA login.
      javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

  2. Unknown User (hujirong)

    Doesn't work with github.com in Jenkins 2.7.1 on Windows 7 64bit:
    stderr: fatal: unable to access 'https://github.com/hujirong/DevOps.git/': SSL certificate problem: self signed certificate in certificate chain

  3. Unknown User (fholtry)

    Doesn't seem to work on Windows with the 2.92 release, either.  But I found a very simple workaround.  I simply ran a job that only ran a windows batch command.  The command to run is the git configure:  git config --global http.sslverify false.  Once it has run, the value is set for all jobs in that Jenkins instance, so you need to be aware this is a security hole.  

  4. Unknown User (savaikar)

    For the Jenkins ver. 2.121.2, you may follow the below steps:

    • Manage Jenkins >> Configure Global Security >> Plugin Manager >> Tick the check-box for "Use browser for metadata download" option