[JIRA] (JENKINS-50300) Can't get Jenkins to recognise self signed Gitlab certs
Title: Message Title Julian Berks closed an issue as Fixed After further testing it seems the rhel java install (via yum) has some form of bug that results in it not using the default trust store. I will continue to investigate but the issue is not with Jenkins. Jenkins / JENKINS-50300 Can't get Jenkins to recognise self signed Gitlab certs Change By: Julian Berks Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-50300) Can't get Jenkins to recognise self signed Gitlab certs
Title: Message Title Julian Berks created an issue Jenkins / JENKINS-50300 Can't get Jenkins to recognise self signed Gitlab certs Issue Type: Bug Assignee: Owen Mehegan Components: gitlab-plugin Created: 2018-03-20 17:28 Environment: Centos - running jenkins 2.107.1 Priority: Major Reporter: Julian Berks Trying to connect Jenkins 2.107.1 to my gitlab install using the jenkins config page. Using a self signed cert on gitlab. Pulled the cert down from gitlab and inserted it in both /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-0.b14.el7_4.x86_64/jre/lib/security/cacerts and /var/lib/jenkins/tools/hudson.model.JDK/jdk_1.8.0_121/jre/lib/security/cacerts but still reports failure to recognise the cert Client error: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Add Comment
